Triple
T33466631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SCCA National Championship Runoffs |
E857065
|
entity |
| Predicate | typeOfTrack |
P3832
|
FINISHED |
| Object | permanent road course |
—
|
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: permanent road course | Statement: [SCCA National Championship Runoffs, typeOfTrack, permanent road course]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfTrack Context triple: [SCCA National Championship Runoffs, typeOfTrack, permanent road course]
-
A.
trackType
chosen
Indicates the specific kind or category of track associated with an entity, such as its functional or physical classification.
-
B.
containsTrackType
Indicates that one entity includes or is associated with a specific type or category of track.
-
C.
composedTrackType
Indicates that one entity is a track whose type or category is defined or characterized by another entity.
-
D.
musicTrack
Indicates a relationship where an entity is identified as a specific music track, typically representing an individual recorded piece of music.
-
E.
musicBrainzType
Indicates the specific MusicBrainz-defined category or classification assigned to an entity within the MusicBrainz database.
- 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00b479c1588190af6e0698b7f8d7f7 |
completed | May 10, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_6a00b4158260819087d0cfad8b18cef4 |
completed | May 10, 2026, 4:36 p.m. |
Created at: May 1, 2026, 1:37 a.m.