Triple
T28858191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tim Birkin |
E728792
|
entity |
| Predicate | vehicleClassDriven |
P165998
|
FINISHED |
| Object | Bentley 4½ Litre |
—
|
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: Bentley 4½ Litre | Statement: [Tim Birkin, vehicleClassDriven, Bentley 4½ Litre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleClassDriven Context triple: [Tim Birkin, vehicleClassDriven, Bentley 4½ Litre]
-
A.
mainVehicleClass
Indicates the primary category or type of vehicle to which an entity chiefly belongs.
-
B.
vehicleType
Indicates the specific kind or category of vehicle associated with an entity (e.g., car, bus, bicycle).
-
C.
intendedVehicleClass
Indicates that one entity is designed or specified to be used with, or is appropriate for, a particular class or category of vehicle.
-
D.
vehicleClassServed
Indicates the class or type of vehicle that a service, facility, or operation is designed to accommodate or serve.
-
E.
vehicleStandard
Indicates that something complies with, or is defined according to, a specified vehicle-related standard or regulatory specification.
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65bb75cd08190bbdb63c093ad6210 |
completed | May 2, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65b136b30819090cf59fb772f35f1 |
completed | May 2, 2026, 8:14 p.m. |
Created at: April 28, 2026, 6:46 a.m.