Triple
T32310299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Civic TV Channel 83 |
E825480
|
entity |
| Predicate | genreOfProgramming |
P179073
|
FINISHED |
| Object | violent programming |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: violent programming | Statement: [Civic TV Channel 83, genreOfProgramming, violent programming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genreOfProgramming Context triple: [Civic TV Channel 83, genreOfProgramming, violent programming]
-
A.
languageOfProgramming
Indicates that one entity is a programming language used to implement, develop, or script the other entity.
-
B.
programmingLanguage
Indicates that one entity is a programming language used to create, control, or interact with the other entity.
-
C.
notableProgrammingCategory
Indicates that an entity is recognized as belonging to a significant or distinguished category within the domain of programming.
-
D.
programmingCategory
Indicates that one entity is classified as a programming-related category or type for the other entity.
-
E.
programLanguage
Indicates that an entity is implemented, written, or expressed using a particular programming language.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71995853c8190912025c0e83640c8 |
completed | May 3, 2026, 9:47 a.m. |
Created at: May 1, 2026, 12:46 a.m.