Triple
T23955201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CARS Tour |
E603768
|
entity |
| Predicate | notableTrackRegion |
P39809
|
FINISHED |
| Object | North Carolina 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: North Carolina short tracks | Statement: [CARS Tour, notableTrackRegion, North Carolina short tracks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTrackRegion Context triple: [CARS Tour, notableTrackRegion, North Carolina short tracks]
-
A.
notableTrack
Indicates that a particular track (such as a song or recording) is especially significant, well-known, or prominent in relation to the subject.
-
B.
notableInRegion
chosen
Indicates that an entity is recognized as notable, prominent, or significant within a specified geographic region.
-
C.
notableTargetArea
Indicates that an action, effect, or focus is specifically directed toward a particularly important or prominent area or region.
-
D.
notableTourRegion
Indicates that an entity is a region recognized as a significant or popular destination for tours or tourism.
-
E.
notableRegionOfSettlement
Indicates that a specified region is a significant or prominent place where an entity is or has been settled.
- 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.