Triple
T23955209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CARS Tour |
E603768
|
entity |
| Predicate | typicalEventSetting |
P97819
|
FINISHED |
| Object | oval short tracks |
—
|
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: oval short tracks | Statement: [CARS Tour, typicalEventSetting, oval short tracks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEventSetting Context triple: [CARS Tour, typicalEventSetting, oval short tracks]
-
A.
typicalVenueSetting
chosen
Indicates the usual or characteristic type of venue or setting in which an event, activity, or interaction typically takes place.
-
B.
typicalEvent
Indicates that the associated event is a common, characteristic, or prototypical occurrence for the given entity or situation.
-
C.
typicalEventDay
Indicates the day on which an event is normally or most commonly held or occurs.
-
D.
typicalSettingConsumed
Indicates the usual context or environment in which something is normally consumed.
-
E.
typicalPerformanceOccasion
Indicates the usual or characteristic type of occasion, event, or context in which a performance typically takes place.
- 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_69e2954222288190a7323554d0cca8d7 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d0d616ec81908c796894f40f3015 |
completed | April 29, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:21 p.m.