Triple
T1770269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESPN2 |
E38857
|
entity |
| Predicate | broadcastsSport |
P6214
|
FINISHED |
| Object | college football |
—
|
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: college football | Statement: [ESPN2, broadcastsSport, college football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastsSport Context triple: [ESPN2, broadcastsSport, college football]
-
A.
sportsProgram
Indicates a relationship where an entity is a sports-related program, event, or broadcast organized or provided by another entity.
-
B.
sportFocus
chosen
Indicates that one entity has a primary emphasis, specialization, or concentration on a particular sport represented by the other entity.
-
C.
specialBroadcasts
Indicates that one entity transmits or airs a broadcast that is designated as special or exceptional in some way to another entity or audience.
-
D.
broadcastsIn
Indicates that one entity transmits or airs content within a particular medium, channel, location, or time frame.
-
E.
broadcastNetwork
Indicates that one entity serves as the television or radio network that broadcasts the programming or content of another 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_69a8862e61708190af97b9838cc3f5de |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab39fc2c448190bfaf1ee8d474632a |
completed | March 6, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69aa61cbb1288190a7ba38b61905f578 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.