Triple
T6255023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El Paso Locomotive FC |
E140140
|
entity |
| Predicate | tierInNationalLeagueSystem |
P42313
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [El Paso Locomotive FC, tierInNationalLeagueSystem, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tierInNationalLeagueSystem Context triple: [El Paso Locomotive FC, tierInNationalLeagueSystem, 2]
-
A.
tierInNationalFootball
Indicates the competitive level or division within a country's national football league system in which an entity (e.g., a club or team) participates.
-
B.
tierInLeagueSystem
chosen
Indicates the specific hierarchical level or division an entity occupies within an organized league system.
-
C.
countryLeagueSystem
Indicates that a particular league system operates within, or is associated with, a specific country.
-
D.
winnerLeagueDivision
Indicates that an entity has won a specific league division in a competitive context.
-
E.
leagueOrCup
Indicates that one entity is a league or cup competition in which the other entity participates or is associated.
- 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_69c008b4858c819095b0199114a9a87b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06363d6008190bf05e003b1f74497 |
completed | March 22, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69c05605566c81908e197f5accd072d2 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:24 p.m.