Triple
T18520968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USRA Light Mikado |
E452580
|
entity |
| Predicate | designedWeightOnDrivers |
P131998
|
FINISHED |
| Object | approximately 220,000 lb |
—
|
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: approximately 220,000 lb | Statement: [USRA Light Mikado, designedWeightOnDrivers, approximately 220,000 lb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedWeightOnDrivers Context triple: [USRA Light Mikado, designedWeightOnDrivers, approximately 220,000 lb]
-
A.
associatedVehicleWeightClass
Indicates the weight classification category that is linked or assigned to a particular vehicle.
-
B.
emptyWeight
Indicates the weight of an object or vehicle when it is empty, excluding any load, cargo, or passengers.
-
C.
weightLimitInKilograms
Indicates the maximum allowable weight for something, expressed in kilograms.
-
D.
hasVehicleWeightLimit
Indicates that there is a maximum allowable weight for vehicles associated with, or permitted to use, a given object or location.
-
E.
weightLimitInPounds
Indicates the maximum allowable weight for something, expressed in pounds.
- 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_69d8d386df84819092355ebb260d848e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5338db5e4819086503a2176dfe499 |
completed | April 19, 2026, 7:57 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:37 a.m.