Triple
T8053796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexican football league system |
E187741
|
entity |
| Predicate | includesReserveTeams |
P71524
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mexican football league system, includesReserveTeams, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesReserveTeams Context triple: [Mexican football league system, includesReserveTeams, yes]
-
A.
hasReserveTeam
Indicates that an organization, typically a sports club, maintains a secondary or backup team formally associated with its main team.
-
B.
hasReserveTeamLeagues
Indicates that an entity’s reserve team participates in, or is associated with, one or more specific sports leagues.
-
C.
alsoIncludesTeamsFrom
Indicates that something not only includes its primary elements but additionally encompasses teams originating from another specified group, category, or source.
-
D.
includesTeam
Indicates that a group, project, or organization has a specific team as one of its constituent members or components.
-
E.
allowsReserveTeamsInPyramid
chosen
Indicates that the competition structure permits reserve teams to participate within the main league pyramid system.
- 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_69ca82b15e948190a62fd7af5218426a |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f9fb8dc8190bacc1f66ddfd1cbf |
completed | March 31, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69cb049a1b9c8190811c396421ebf9c9 |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:25 p.m.