Triple
T15284908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cruisin’ The Coast |
E365367
|
entity |
| Predicate | targetVehicleEra |
P117957
|
FINISHED |
| Object | classic era vehicles |
—
|
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: classic era vehicles | Statement: [Cruisin’ The Coast, targetVehicleEra, classic era vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetVehicleEra Context triple: [Cruisin’ The Coast, targetVehicleEra, classic era vehicles]
-
A.
vehicleGeneration
Indicates the generational version or iteration of a vehicle within a model line or series.
-
B.
propulsionEra
Indicates the historical period or generation of propulsion technology associated with an entity (e.g., vehicle, engine, or system).
-
C.
rollingStockEra
Indicates the historical or operational time period during which a particular piece of rolling stock is designed to represent or is considered appropriate.
-
D.
carGeneration
Indicates the specific model generation or version of a car within its production lineage.
-
E.
aircraftEra
Indicates the historical time period or era during which an aircraft was designed, produced, or primarily operated.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00e53c9588190a6cb61ac8805c706 |
completed | April 15, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2e413481909d9180a8d78d2c17 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:15 a.m.