Triple
T32608476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1966 Geneva Motor Show |
E833588
|
entity |
| Predicate | exhibitedVehicleType |
P1776
|
FINISHED |
| Object | sports 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: sports cars | Statement: [1966 Geneva Motor Show, exhibitedVehicleType, sports cars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exhibitedVehicleType Context triple: [1966 Geneva Motor Show, exhibitedVehicleType, sports cars]
-
A.
vehicleType
chosen
Indicates the specific kind or category of vehicle associated with an entity (e.g., car, bus, bicycle).
-
B.
listedVehicle
Indicates that a vehicle has been placed on a list, such as a registry, catalog, or inventory, as part of a tracking or management process.
-
C.
heritageVehicleType
Indicates the specific category or type of a vehicle that is considered part of cultural, historical, or heritage transport.
-
D.
intendedVehicleClass
Indicates that one entity is designed or specified to be used with, or is appropriate for, a particular class or category of vehicle.
-
E.
controlCarType
Indicates a relationship where an entity has authority to operate, manage, or make decisions about a specific type or category of car.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c6c91a1c819097d51d2a159e223b |
completed | May 3, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:05 a.m.