Triple
T2993330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MKE Ankaragücü |
E81006
|
entity |
| Predicate | traditionalLeagueLevel |
P10472
|
FINISHED |
| Object | top tier of Turkish football |
—
|
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: top tier of Turkish football | Statement: [MKE Ankaragücü, traditionalLeagueLevel, top tier of Turkish football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalLeagueLevel Context triple: [MKE Ankaragücü, traditionalLeagueLevel, top tier of Turkish football]
-
A.
eligibleLeague
Indicates that an entity (such as a team or player) is qualified or permitted to participate in a particular league.
-
B.
leagueType
chosen
Indicates the classification or category of a league within a broader organizational or competitive structure.
-
C.
aboveLeague
Indicates that one entity is in a higher league, tier, or competitive level than another.
-
D.
developmentLeagueFor
Indicates that one entity serves as a developmental or minor league affiliate for another, typically higher-level, sports team or organization.
-
E.
stateLeague
Indicates that a sports team or club competes in, or is affiliated with, a particular state-level league or competition.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99e12c5c8190af7cc20e4c48bf45 |
completed | March 8, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ad961403108190bbecb8d3608fd4e0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.