Triple
T20205847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Pacific Big Boy class locomotives |
E493346
|
entity |
| Predicate | weightOnDrivers |
P1575
|
FINISHED |
| Object | about 540,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: about 540,000 lb | Statement: [Union Pacific Big Boy class locomotives, weightOnDrivers, about 540,000 lb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weightOnDrivers Context triple: [Union Pacific Big Boy class locomotives, weightOnDrivers, about 540,000 lb]
-
A.
designedWeightOnDrivers
Indicates that something specifies or imposes a particular weight load intended to rest on the drivers (driving wheels or driver components) of a vehicle or machine.
-
B.
associatedVehicleWeightClass
Indicates the weight classification category that is linked or assigned to a particular vehicle.
-
C.
drivesOn
Indicates that an entity uses or travels along a particular route, surface, or roadway as its path of movement.
-
D.
weight
chosen
Indicates a relationship where a numerical value quantifies how heavy an entity is, often used to measure or compare mass or load.
-
E.
weightLimitInPounds
Indicates the maximum allowable weight for something, expressed in pounds.
- 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66d922ebc8190ae012da8ceba74dd |
completed | April 20, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:38 p.m.