Triple
T29327450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riverside International Raceway |
E743690
|
entity |
| Predicate | hadConfiguration |
P13644
|
FINISHED |
| Object | long course with esses |
—
|
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: long course with esses | Statement: [Riverside International Raceway, hadConfiguration, long course with esses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadConfiguration Context triple: [Riverside International Raceway, hadConfiguration, long course with esses]
-
A.
hasConfiguration
chosen
Indicates that an entity is associated with or defined by a particular configuration or setup.
-
B.
hadCustom
Indicates that an entity previously possessed or was associated with a customized or user-defined version of something.
-
C.
hadBase
Indicates that an entity maintained or operated from a particular base location or primary site.
-
D.
hadModel
Indicates that an entity possessed, used, or was associated with a particular model (e.g., a product, design, or version) at some point in time.
-
E.
hadFormat
Indicates that a resource was previously available in a different format or media type than it is now.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6689782388190a36b98ec2d60d63f |
completed | May 2, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 1:27 p.m.