Triple
T16265185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N700-8000 series |
E394856
|
entity |
| Predicate | hasCarClass |
P122426
|
FINISHED |
| Object | ordinary class |
—
|
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: ordinary class | Statement: [N700-8000 series, hasCarClass, ordinary class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCarClass Context triple: [N700-8000 series, hasCarClass, ordinary class]
-
A.
intendedVehicleClass
Indicates that one entity is designed or specified to be used with, or is appropriate for, a particular class or category of vehicle.
-
B.
hasCabType
Indicates that an entity is associated with or characterized by a specific type or category of cab.
-
C.
automotiveClassSupported
Indicates that a particular automotive class or category is supported or compatible within a given context or system.
-
D.
mainVehicleClass
Indicates the primary category or type of vehicle to which an entity chiefly belongs.
-
E.
hasVehicle
Indicates that one entity possesses, owns, or is assigned a vehicle.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c73944819085633e6d2a69bae9 |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:05 a.m.