Triple
T2349759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indy Eleven |
E47418
|
entity |
| Predicate | previousLeagueLevel |
P5927
|
FINISHED |
| Object | second division NASL |
—
|
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: second division NASL | Statement: [Indy Eleven, previousLeagueLevel, second division NASL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousLeagueLevel Context triple: [Indy Eleven, previousLeagueLevel, second division NASL]
-
A.
successorLeagueLevel
Indicates that one league level directly follows another in a hierarchical sequence, representing the next higher or lower tier in the league structure.
-
B.
aboveLeague
Indicates that one entity is in a higher league, tier, or competitive level than another.
-
C.
belowLeague
Indicates that one entity is in a lower league, division, or competitive tier than another entity.
-
D.
playedInLeagueThatBecame
Indicates that an entity participated in a sports league which later transformed into, merged into, or was rebranded as another specified league.
-
E.
formerLeague
chosen
Indicates that an entity previously belonged to or participated in a particular league but is no longer a member.
- 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_69a88a1b678c8190bce986922ba60ce0 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abcb802da08190980100444010f91e |
completed | March 7, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69abc5981ce48190a3f7852d28276e11 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:54 p.m.