Triple
T19681068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grugliasco |
E472585
|
entity |
| Predicate | hasVehicleIndustryHeritage |
P2411
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Grugliasco, hasVehicleIndustryHeritage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVehicleIndustryHeritage Context triple: [Grugliasco, hasVehicleIndustryHeritage, true]
-
A.
heritageVehicleType
Indicates the specific category or type of a vehicle that is considered part of cultural, historical, or heritage transport.
-
B.
hasIndustrialHeritage
chosen
Indicates that an entity possesses or is associated with historically significant industrial sites, structures, or practices.
-
C.
historicRacingCar
Indicates that an entity is a racing car of historical significance, typically from a past era of motorsport competition.
-
D.
hasBusinessHeritage
Indicates that an entity possesses a historical or traditional connection to a particular business, company, or commercial lineage.
-
E.
hasVehicularUse
Indicates that something is used for, intended for, or associated with operation by vehicles or vehicular traffic.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e641bf97348190bc31b00ed4ec6cad |
completed | April 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:45 p.m.