Triple
T11206171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irapuato |
E265167
|
entity |
| Predicate | leagueLevelHistory |
P50168
|
FINISHED |
| Object | lower divisions of Mexican 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: lower divisions of Mexican football | Statement: [Irapuato, leagueLevelHistory, lower divisions of Mexican football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueLevelHistory Context triple: [Irapuato, leagueLevelHistory, lower divisions of Mexican football]
-
A.
roleInLeagueHistory
Indicates the specific function, contribution, or significance an entity has had within the historical development or narrative of a league.
-
B.
associatedLeagueLevel
chosen
Indicates that one entity is linked to another entity representing the competitive tier or level of a sports league.
-
C.
teamHistory
Indicates that there exists a historical relationship or record connecting a team with its past events, compositions, or performance over time.
-
D.
teamLevel
Indicates the hierarchical rank or tier at which a team operates within an organization, competition, or structure.
-
E.
hasCompetitionHistory
Indicates that an entity has a recorded history of participation in competitions or competitive events.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d4eef88190a7f05bca82d919b9 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.