Triple
T1356353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Broadcasting Company |
E28997
|
entity |
| Predicate | notableProgramGenre |
P20471
|
FINISHED |
| Object | news |
—
|
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: news | Statement: [American Broadcasting Company, notableProgramGenre, news]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableProgramGenre Context triple: [American Broadcasting Company, notableProgramGenre, news]
-
A.
notableProgramType
chosen
Indicates that the subject is recognized for or associated with a particular type or category of program.
-
B.
notableSeries
Indicates that an entity is a significant or well-known installment within a particular series or franchise.
-
C.
notableShow
Indicates that a show is especially prominent, distinguished, or significant in some noteworthy way.
-
D.
notableWorkGenre
Indicates that a particular work is recognized as notable for an entity and specifies the genre to which that work belongs.
-
E.
notableMedia
Indicates a relationship where a media work is recognized as significant, prominent, or especially relevant in connection with a given entity.
- F. None of above.
Provenance (3 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_69a498d77abc8190913bf57e5f51d2c4 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c28c8dd0819082f94c9e7c837c5f |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef7700c819099b294e8d9320e70 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.