Triple
T27096760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liga MX Apertura 2021 |
E686324
|
entity |
| Predicate | previousTitleForAtlas |
P2939
|
FINISHED |
| Object | 1951 Liga MX title |
—
|
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: 1951 Liga MX title | Statement: [Liga MX Apertura 2021, previousTitleForAtlas, 1951 Liga MX title]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousTitleForAtlas Context triple: [Liga MX Apertura 2021, previousTitleForAtlas, 1951 Liga MX title]
-
A.
previousTitle
chosen
Indicates that one title held or used by an entity directly preceded another title in sequence or time.
-
B.
previousSingleTitle
Indicates that the referenced title is the immediately preceding single released before the current one.
-
C.
earlyTitleOf
Indicates that one entity served as an earlier or preliminary title for another entity.
-
D.
predecessorTitleContext
Indicates that the relationship specifies the contextual circumstances (such as role, period, or setting) under which a predecessor’s title is relevant or applies.
-
E.
replacedEarlierTitle
Indicates that one title or designation has been superseded by an earlier title that it replaced in a sequence of naming or labeling.
- 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_69ef1489f8b481908e24a1985982bd26 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 27, 2026, 8:44 a.m.