Triple
T26317187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eagles |
E662003
|
entity |
| Predicate | governsSportsFor |
P98940
|
FINISHED |
| Object | Emory University |
—
|
NE NERFINISHED |
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: Emory University | Statement: [Eagles, governsSportsFor, Emory University]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governsSportsFor Context triple: [Eagles, governsSportsFor, Emory University]
-
A.
sportTypeGoverned
Indicates that a governing body or organization has regulatory authority over a particular type of sport.
-
B.
governsSportLevel
Indicates that one entity has authority to set, control, or regulate the competitive level or tier at which a sport or sporting activity is conducted.
-
C.
overseesSport
chosen
Indicates that one entity has responsibility for supervising, managing, or regulating a particular sport or sporting activity.
-
D.
sportGoverningBody
Indicates that one entity serves as the official governing or regulatory organization responsible for overseeing and managing a particular sport or sports activity associated with another entity.
-
E.
officiatedSport
Indicates that an entity served as an official (e.g., referee, umpire, judge) in the context of a specified sport.
- 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: April 26, 2026, 10:25 p.m.