Triple
T36076081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaguar XK platform |
E1043497
|
entity |
| Predicate | productionVehicleStart |
P101552
|
FINISHED |
| Object | Jaguar XK (X150) 2005 |
—
|
NE NERFINISHED |
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: Jaguar XK (X150) 2005 | Statement: [Jaguar XK platform, productionVehicleStart, Jaguar XK (X150) 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionVehicleStart Context triple: [Jaguar XK platform, productionVehicleStart, Jaguar XK (X150) 2005]
-
A.
producedVehicle
chosen
Indicates that one entity manufactured or created a particular vehicle.
-
B.
carsStarted
Indicates that one or more cars have been initiated into operation, typically by turning on their engines.
-
C.
enteredAutomobileProduction
Indicates that an entity began manufacturing automobiles as a commercial or industrial activity.
-
D.
powertrainProduction
Indicates a relationship where an entity is involved in the manufacturing or assembly of a vehicle’s powertrain components.
-
E.
vehicleBase
Indicates that one entity serves as the foundational or underlying base for a vehicle-related entity or system.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fee691952c8190822da83e46311d1d |
completed | May 9, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69fee62f285c8190a625562a9b80526e |
completed | May 9, 2026, 7:45 a.m. |
Created at: May 3, 2026, 4:08 p.m.