Triple
T35330111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASCAR Cup Series owners’ championship |
E1020293
|
entity |
| Predicate | hasMultipleDriversPerCarPossible |
P183019
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [NASCAR Cup Series owners’ championship, hasMultipleDriversPerCarPossible, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleDriversPerCarPossible Context triple: [NASCAR Cup Series owners’ championship, hasMultipleDriversPerCarPossible, true]
-
A.
hasMultipleRideScenarios
Indicates that an entity is associated with more than one distinct ride scenario or configuration.
-
B.
minimumDriversPerCar
Indicates the minimum number of drivers that must be assigned to or available for each car.
-
C.
driversMayShareCar
chosen
Indicates that multiple drivers are permitted to use or share the same car.
-
D.
usesPassengerCars
Indicates that an entity operates or employs passenger cars as part of its activities or services.
-
E.
possibleDriver
Indicates that an entity is a candidate or potential driver of another entity, such as a possible cause, regulator, or influencing factor.
- 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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: May 3, 2026, 4:03 p.m.