Triple
T22393454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White City Rebels |
E553567
|
entity |
| Predicate | competedInTier |
P43092
|
FINISHED |
| Object | top tier of UK speedway |
—
|
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: top tier of UK speedway | Statement: [White City Rebels, competedInTier, top tier of UK speedway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competedInTier Context triple: [White City Rebels, competedInTier, top tier of UK speedway]
-
A.
involvesCompetitionLevel
Indicates that the relationship or action specifies or depends on a particular degree or intensity of competition involved.
-
B.
competitionHierarchyLevel
chosen
Indicates the relative rank or tier of a competition within an overall competitive structure or hierarchy.
-
C.
competedAs
Indicates that an entity participated in a competition or contest in the role, category, or capacity specified by another entity.
-
D.
competedFor
Indicates that an entity took part in a contest, rivalry, or competition in pursuit of another entity (such as a prize, position, or resource).
-
E.
regionCompetedIn
Indicates the geographic region or area where an entity participated in a competition or contest.
- 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_69e11e4cf87c8190a1ff474daec326b7 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1585ce39c819082b62e7f2e297d9b |
completed | April 29, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69e73015484c8190a9a0b9f554b61a81 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.