Triple
T33421563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1967 Ford Mustang Shelby GT500 "Eleanor" |
E855859
|
entity |
| Predicate | productionCarsBuiltForFilm |
P196637
|
FINISHED |
| Object | multiple units |
—
|
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 units | Statement: [1967 Ford Mustang Shelby GT500 "Eleanor", productionCarsBuiltForFilm, multiple units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionCarsBuiltForFilm Context triple: [1967 Ford Mustang Shelby GT500 "Eleanor", productionCarsBuiltForFilm, multiple units]
-
A.
carNumberInFilm
Indicates the specific identifying number assigned to a car as it appears within a particular film.
-
B.
hasFictionalVehicle
Indicates that one entity possesses, controls, or is associated with a vehicle that exists only in a fictional or imaginary context.
-
C.
vehicleDrivenInFiction
Indicates that a vehicle is depicted as being driven or operated within a fictional work or narrative.
-
D.
producedVehicle
Indicates that one entity manufactured or created a particular vehicle.
-
E.
notableCar
Indicates that the subject is a car recognized for its significance, prominence, or special interest (e.g., historically, culturally, or technically).
- 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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
| PDg | Predicate description generation | batch_69fe5ec84910819094cb15269ace7c51 |
completed | May 8, 2026, 10:08 p.m. |
Created at: May 1, 2026, 1:36 a.m.