Triple
T5609474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Albirex Niigata |
E147315
|
entity |
| Predicate | relegationToJ2 |
P64632
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Albirex Niigata, relegationToJ2, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relegationToJ2 Context triple: [Albirex Niigata, relegationToJ2, 2017]
-
A.
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.
-
B.
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.
-
C.
relegationIntroduced
Indicates that a system or competition has implemented a mechanism by which lower-performing participants are demoted to a lower tier or division.
-
D.
demotedToSecondTierBy
Indicates that an entity’s status, rank, or priority has been reduced by another entity to a secondary or lower tier.
-
E.
relegatedFromBPoolPreviousYear
Indicates that an entity was demoted or dropped from the B Pool in the previous year.
- F. None of above. chosen
Provenance (4 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_69c0090500f881908374285baf0ac46f |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020fe7ee0819088ced51afd9a4f93 |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1b3c98819080687d18ab10a914 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0684908190ae2d14f0bd2ab892 |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:39 p.m.