Triple
T34803851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yas Marina 12 Hours |
E1003293
|
entity |
| Predicate | driverChanges |
P180438
|
FINISHED |
| Object | multiple driver changes per car |
—
|
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: multiple driver changes per car | Statement: [Yas Marina 12 Hours, driverChanges, multiple driver changes per car]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: driverChanges Context triple: [Yas Marina 12 Hours, driverChanges, multiple driver changes per car]
-
A.
allowsDriverChanges
chosen
Indicates that the arrangement or system permits one driver to be replaced or substituted by another.
-
B.
engineChanges
Indicates that an entity undergoes a modification or replacement of its engine.
-
C.
featureChange
Indicates a modification in the properties, characteristics, or attributes of an entity between two states or points in time.
-
D.
drivetrainChangeDescription
Indicates a description of a modification or change made to a vehicle’s drivetrain system.
-
E.
successorBodyStyleChange
Indicates that one body style directly follows and replaces another in a sequence of design or model changes.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77a8bcfa48190ad0f0df94b2301f8 |
completed | May 3, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_69f7795b1abc8190823664d1caa94649 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.