Triple
T13288412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Great Race |
E316500
|
entity |
| Predicate | driverFormat |
P29567
|
FINISHED |
| Object | two-driver endurance format |
—
|
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: two-driver endurance format | Statement: [The Great Race, driverFormat, two-driver endurance format]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: driverFormat Context triple: [The Great Race, driverFormat, two-driver endurance format]
-
A.
driveType
Indicates the type or configuration of the drive mechanism used to power or propel an entity.
-
B.
driverType
chosen
Indicates the category or role of a driver associated with an entity or activity (e.g., primary, backup, commercial, etc.).
-
C.
driveScheme
Indicates that one entity operates or controls a scheme, system, or initiative, causing it to function or move forward.
-
D.
driverFor
Indicates that one entity serves as the driver or operator of a vehicle or transport service for another entity.
-
E.
drives
Indicates that one entity operates and controls the movement of a vehicle or similar conveyance transporting themselves or others.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:27 p.m.