Triple
T32069399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Fabulous Hudson Hornet |
E818968
|
entity |
| Predicate | inCars3 |
P173182
|
FINISHED |
| Object | appears in flashbacks |
—
|
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: appears in flashbacks | Statement: [The Fabulous Hudson Hornet, inCars3, appears in flashbacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inCars3 Context triple: [The Fabulous Hudson Hornet, inCars3, appears in flashbacks]
-
A.
LeMansCar
Indicates that something is a car designed, built, or used for participation in the 24 Hours of Le Mans endurance race.
-
B.
spinningCars
Indicates that one or more cars are rotating or spinning, rather than moving straightforwardly.
-
C.
رمز لوحة المركبات
Indicates a relationship where a specific code or identifier is assigned to a vehicle’s license plate.
-
D.
poweredCar
Indicates that one entity is a car whose operation or movement is enabled or driven by another entity as its power source.
-
E.
raceComponent
Indicates that one entity is a constituent part, segment, or stage within a larger race or racing event involving another entity.
- F. None of above. chosen
Provenance (4 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b522fe4c819093c731ec03756536 |
completed | May 3, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69f6b154b3dc819087115f5f63f7b00f |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b267b90c8190807208cadce5ae8d |
completed | May 3, 2026, 2:26 a.m. |
Created at: May 1, 2026, 12:23 a.m.