Triple
T28461161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liga Premier de México |
E720157
|
entity |
| Predicate | formerLevelInPyramid |
P3194
|
FINISHED |
| Object | second tier |
—
|
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: second tier | Statement: [Liga Premier de México, formerLevelInPyramid, second tier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerLevelInPyramid Context triple: [Liga Premier de México, formerLevelInPyramid, second tier]
-
A.
levelOnPyramid
chosen
Indicates the relative vertical tier or layer that an entity occupies within a pyramid structure.
-
B.
representedLevel
Indicates that one entity denotes or encodes the degree, intensity, or value (i.e., the level) of another entity or property.
-
C.
stratigraphicLevelNumber
Indicates the specific numbered position or order of a layer within a stratigraphic sequence.
-
D.
ringHierarchyLevel
Indicates the position or rank of an entity within a structured ring-based hierarchy.
-
E.
relativeLevel
Indicates a comparative relationship specifying how one entity’s level, degree, or intensity of some property stands relative to that of another entity.
- 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_69f01a58a67c819097936d9e8da8d6e6 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fdd2be648c8190b60b3d1caeb44364 |
completed | May 8, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69fdd14a5c708190a6f95ec61f4fc28f |
completed | May 8, 2026, 12:04 p.m. |
Created at: April 28, 2026, 2:40 a.m.