Triple
T5392090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bradford Bulls |
E120352
|
entity |
| Predicate | notableCompetitionFormat |
P2673
|
FINISHED |
| Object | play-offs |
—
|
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: play-offs | Statement: [Bradford Bulls, notableCompetitionFormat, play-offs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCompetitionFormat Context triple: [Bradford Bulls, notableCompetitionFormat, play-offs]
-
A.
competitionFormat
chosen
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
B.
affectedCompetitionFormat
Indicates that one entity caused a change or influence on the structure, rules, or format of a competition.
-
C.
notableTournament
Indicates that an entity is a tournament of particular significance or prominence in relation to another entity.
-
D.
replacedCompetitionFormat
Indicates that one competition format was substituted for and took the place of another competition format.
-
E.
tourFormat
Indicates the specific structure, style, or type of a tour associated with an 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_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.