Triple
T28266042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liga II |
E712705
|
entity |
| Predicate | positionRelativeToLiga I |
P101018
|
FINISHED |
| Object | directly below |
—
|
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: directly below | Statement: [Liga II, positionRelativeToLiga I, directly below]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeToLiga I Context triple: [Liga II, positionRelativeToLiga I, directly below]
-
A.
positionInLeagueSystem
Indicates the rank or tier an entity holds within an organized league or competitive system.
-
B.
relativePositionInStadium
Indicates the spatial relationship between entities based on where they are located relative to each other within a stadium.
-
C.
positionRelativeToHod
Indicates the spatial or positional relationship of an entity with respect to a specified hod (a particular reference point or unit in a structured space).
-
D.
positionInLineup
Indicates the specific ordered place an entity occupies within a lineup or sequence of entities.
-
E.
locatedInLeagueStructure
chosen
Indicates that an entity occupies a specific position or level within an organized league’s hierarchical structure.
- 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_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 27, 2026, 11:14 p.m.