Triple
T21754989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montedio Yamagata |
E537014
|
entity |
| Predicate | relegationFromJ1 |
P64632
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Montedio Yamagata, relegationFromJ1, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relegationFromJ1 Context triple: [Montedio Yamagata, relegationFromJ1, 2011]
-
A.
relegationToJ2
chosen
Indicates that a team or club is demoted from a higher football division to Japan’s J2 League.
-
B.
relegationFromSecondTierTo
Indicates that an entity is demoted from the second-highest competitive level or division to a specified lower tier or league.
-
C.
relegatedFrom
Indicates that an entity has been demoted, downgraded, or moved from a higher status, level, or position to a lower one, typically as a result of performance or evaluation.
-
D.
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.
-
E.
relegationHistory
Indicates that one entity has a documented record of being moved to a lower status, tier, or division within a hierarchical system over time.
- 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01d8d6d0081908e0ccfbccea58895 |
completed | April 28, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69e6969e46088190b13d6e9025775ea3 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:50 p.m.