Triple
T17376757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2. Liga |
E422456
|
entity |
| Predicate | relegationPlayoffWith |
P31084
|
FINISHED |
| Object | 3. Liga |
—
|
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: 3. Liga | Statement: [2. Liga, relegationPlayoffWith, 3. Liga]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relegationPlayoffWith Context triple: [2. Liga, relegationPlayoffWith, 3. Liga]
-
A.
relegationRound
Indicates that entities are involved in a stage or match of a competition where participants risk being demoted to a lower division or tier.
-
B.
hasRelegationPlayOff
chosen
Indicates that an entity is involved in or assigned to a relegation play-off match or series to determine its league status.
-
C.
relegationSystem
Indicates a system in which entities are moved to a lower tier or level based on their performance or ranking within a structured hierarchy.
-
D.
playoffRound
Indicates the specific stage or round within a playoff series in which a game, matchup, or event takes place.
-
E.
playoffQualification
Indicates that an entity has secured a position to participate in a postseason playoff competition based on qualifying criteria.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a6ddbd081908908b953597977d2 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.