Triple
T37001445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Ten Conference football championship trophy |
E915360
|
entity |
| Predicate | formerNameInUse |
P25649
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Big Ten Conference football championship trophy, formerNameInUse, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerNameInUse Context triple: [Big Ten Conference football championship trophy, formerNameInUse, 2011]
-
A.
formerName
Indicates that an entity was previously known by a different name in the past.
-
B.
previousNameUsedUntil
chosen
Indicates that a particular name was used for an entity up to (but not necessarily including) a specified end date or time.
-
C.
formerMemberName
Indicates that the referenced name belongs to an entity that was previously a member of a particular group, organization, or body but is no longer one.
-
D.
heldAtFormerName
Indicates that an event or activity took place at a location when it was known by a previous or former name.
-
E.
historicalNameUsedIn
Indicates that a historical or former name was used to refer to a particular entity in some context.
- 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a00b8e0a5508190abc5c1e492bed12e |
completed | May 10, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_6a00b8327d048190850af317f60f0f8b |
completed | May 10, 2026, 4:54 p.m. |
Created at: May 3, 2026, 4:14 p.m.