Triple
T23169600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | black No. 3 Goodwrench Chevrolet |
E578807
|
entity |
| Predicate | associatedWithTrackType |
P3832
|
FINISHED |
| Object | oval 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 tracks | Statement: [black No. 3 Goodwrench Chevrolet, associatedWithTrackType, oval tracks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithTrackType Context triple: [black No. 3 Goodwrench Chevrolet, associatedWithTrackType, oval tracks]
-
A.
associatedWithTrack
Indicates a relationship in which an entity is linked or connected to a specific track, such as being part of, derived from, or relevant to that track.
-
B.
containsTrackType
Indicates that one entity includes or is associated with a specific type or category of track.
-
C.
trackType
chosen
Indicates the specific kind or category of track associated with an entity, such as its functional or physical classification.
-
D.
associatedWithArtistType
Indicates that an entity has a connection or linkage to a particular category or type of artist.
-
E.
associatedWithTransactionType
Indicates that something has a connection or linkage to a specific type or category of transaction.
- 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_69e245fc75348190a0288401044c8af8 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f2f10208190b3a0f9a4c790cb0a |
completed | April 29, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:03 p.m.