Triple
T28266060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liga II |
E712705
|
entity |
| Predicate | associatedTopDivision |
P91097
|
FINISHED |
| Object | Liga I |
—
|
NE NERFINISHED |
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: Liga I | Statement: [Liga II, associatedTopDivision, Liga I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedTopDivision Context triple: [Liga II, associatedTopDivision, Liga I]
-
A.
topDivisionLinked
Indicates that there exists a direct or relevant linkage between an entity and its highest-level (top) division within an organizational or hierarchical structure.
-
B.
topDivisionOf
Indicates that one administrative or organizational unit is the highest-level division within the structure of another entity.
-
C.
topDivision
Indicates that an entity belongs to the highest-level division or tier within a hierarchical structure.
-
D.
previousTopDivisionOf
Indicates that an entity was formerly in the highest-level division or tier of a given organizational or competitive structure.
-
E.
topDivisionAbove
chosen
Indicates that one division or tier is hierarchically higher or superior to another within an organizational or structural ranking.
- 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_6a0116ca6a1c81909a9e938dbe54eb8a |
completed | May 10, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_6a0116655e248190bdfe5b4bb4f1cf47 |
completed | May 10, 2026, 11:36 p.m. |
Created at: April 27, 2026, 11:14 p.m.