Triple
T32630192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buntingford Classic Car Show |
E834182
|
entity |
| Predicate | typicalVehiclesShown |
P205123
|
FINISHED |
| Object | vintage cars |
—
|
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: vintage cars | Statement: [Buntingford Classic Car Show, typicalVehiclesShown, vintage cars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalVehiclesShown Context triple: [Buntingford Classic Car Show, typicalVehiclesShown, vintage cars]
-
A.
depictsVehicle
Indicates that one entity visually represents or portrays a vehicle in an image, artwork, or other depiction.
-
B.
vehicleStandard
Indicates that something complies with, or is defined according to, a specified vehicle-related standard or regulatory specification.
-
C.
poweredVehicleFamily
Indicates that one vehicle is part of a family or group of vehicles that share a common powered (motorized) design or platform.
-
D.
producedVehicle
Indicates that one entity manufactured or created a particular vehicle.
-
E.
vehicleBase
Indicates that one entity serves as the foundational or underlying base for a vehicle-related entity or system.
- 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_69f3492dc2308190a88c6e30a3f3f576 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037cab06288190b093935f235ddff2 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 1:07 a.m.