Triple
T5392100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bradford Bulls |
E120352
|
entity |
| Predicate | relegationSeason |
P34123
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Bradford Bulls, relegationSeason, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relegationSeason Context triple: [Bradford Bulls, relegationSeason, 2014]
-
A.
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.
-
B.
relegatedFrom
chosen
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.
-
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.
typicalRelegatedTeamsPerSeason
Indicates the usual or average number of teams that are relegated from a league in a single season.
-
E.
relegatedFromBPoolPreviousYear
Indicates that an entity was demoted or dropped from the B Pool in the previous year.
- 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_69bd46354c648190a38b26f107010a96 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd8719ff04819089e3a90f90b5e3fc |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd8463a9c88190bd760378f3026180 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:04 p.m.