Triple
T12805496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TFF First League |
E306133
|
entity |
| Predicate | usesRelegation |
P9667
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [TFF First League, usesRelegation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRelegation Context triple: [TFF First League, usesRelegation, yes]
-
A.
hasRelegationTo
chosen
Indicates that an entity is demoted or moved down to a lower level, tier, or division within a hierarchical system.
-
B.
canDelegateTo
Indicates that one entity has the authority or ability to transfer or assign its responsibilities, tasks, or decision-making power to another entity.
-
C.
hasRelegationHistory
Indicates that an entity has experienced one or more relegations in its competitive or hierarchical history.
-
D.
mayBeDelegatedTo
Indicates that a responsibility, task, or authority can be transferred from one entity to another to act on its behalf.
-
E.
mayDelegateTo
Indicates that one entity is permitted to transfer or assign its authority, responsibility, or rights to another entity.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e7f370c8190b3fc39c1b63394c6 |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:31 p.m.