Triple
T31380752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bandimere Speedway |
E800445
|
entity |
| Predicate | hasChristmasTree |
P194370
|
FINISHED |
| Object | standard drag racing starting light system |
—
|
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: standard drag racing starting light system | Statement: [Bandimere Speedway, hasChristmasTree, standard drag racing starting light system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChristmasTree Context triple: [Bandimere Speedway, hasChristmasTree, standard drag racing starting light system]
-
A.
hasChristmasSetting
Indicates that an event, scene, or work takes place during or is thematically set around the Christmas holiday period.
-
B.
hasChristmasMarket
Indicates that a place or entity hosts or features a Christmas market.
-
C.
hasSeasonalDecorations
Indicates that an entity is adorned with decorations that are specific to a particular season or holiday period.
-
D.
hasAdventCalendar
Indicates that one entity possesses or is associated with an advent calendar related to another entity or context.
-
E.
hasTrees
Indicates that something possesses or contains one or more trees.
- 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_69f224e84da08190abfc2f17494a33c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
| PDg | Predicate description generation | batch_69fd6dbc3ac0819093fbcfe95f12b93d |
completed | May 8, 2026, 4:59 a.m. |
Created at: April 29, 2026, 9:18 p.m.