Triple
T27796221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dakota Wizards (franchise lineage) |
E702116
|
entity |
| Predicate | finalIdentity |
P142451
|
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: [Dakota Wizards (franchise lineage), finalIdentity, Iowa Energy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalIdentity Context triple: [Dakota Wizards (franchise lineage), finalIdentity, Iowa Energy]
-
A.
originalIdentity
Indicates that one entity represents the initial or true identity from which another entity is derived, transformed, or aliased.
-
B.
publicIdentity
Indicates that an entity’s outward-facing identity or persona is known, presented, or recognized in a public context.
-
C.
futureIdentity
Indicates that one entity will become identical to or the same as another entity at some point in the future.
-
D.
subjectIdentity
Indicates that two or more references correspond to the same underlying entity or individual identity.
-
E.
returnsToIdentityOf
chosen
Indicates that an entity reverts or is restored to its original or defining identity after a change, transformation, or deviation.
- 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_69ef8408e0588190977cffa32dc33a29 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 27, 2026, 5:31 p.m.