Triple
T30145261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAN TGM |
E766236
|
entity |
| Predicate | typicalGrossVehicleWeightRange |
P90341
|
FINISHED |
| Object | 13–26 tonnes |
—
|
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: 13–26 tonnes | Statement: [MAN TGM, typicalGrossVehicleWeightRange, 13–26 tonnes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGrossVehicleWeightRange Context triple: [MAN TGM, typicalGrossVehicleWeightRange, 13–26 tonnes]
-
A.
announcedGrossVehicleWeightRating
Indicates that an entity has a specified gross vehicle weight rating that has been formally announced or declared.
-
B.
typicalCarWeight
Indicates the usual or characteristic weight associated with a given car.
-
C.
associatedVehicleWeightClass
Indicates the weight classification category that is linked or assigned to a particular vehicle.
-
D.
typicalTruckWeightRange
chosen
Indicates the usual minimum-to-maximum weight interval that trucks of a given type or category are expected to fall within.
-
E.
vehicleSizeRange
Indicates the range of sizes (e.g., dimensions, capacity, or weight class) within which a vehicle falls.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:18 p.m.