Triple
T27886370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2011 NBA D-League Championship |
E705234
|
entity |
| Predicate | wasFirstTitleFor |
P12405
|
FINISHED |
| Object | Iowa Energy |
—
|
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: Iowa Energy | Statement: [2011 NBA D-League Championship, wasFirstTitleFor, Iowa Energy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFirstTitleFor Context triple: [2011 NBA D-League Championship, wasFirstTitleFor, Iowa Energy]
-
A.
wasFirstOf
Indicates that the subject is the earliest or initial instance in a series, sequence, or group of similar entities or events.
-
B.
firstUseAsTitleBy
Indicates that an entity is the first to use a given term, phrase, or designation as a formal title for another entity.
-
C.
wasFirst
Indicates that one entity occurred, appeared, or held a position before another in time or sequence.
-
D.
firstTitleSince
Indicates that an entity has achieved a particular title for the first time since a specified earlier point, event, or prior title occurrence.
-
E.
firstTitleFor
chosen
Indicates that one entity is the earliest or primary title assigned to another entity, typically among multiple possible titles.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 6:33 p.m.