Triple
T6810599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeep Gladiator |
E156620
|
entity |
| Predicate | payloadCapacityMax |
P10871
|
FINISHED |
| Object | over 1,600 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: over 1,600 lb | Statement: [Jeep Gladiator, payloadCapacityMax, over 1,600 lb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payloadCapacityMax Context triple: [Jeep Gladiator, payloadCapacityMax, over 1,600 lb]
-
A.
maximumPayload
chosen
Indicates the greatest amount of load or capacity that an entity is designed or allowed to carry, handle, or support.
-
B.
maximumPassengerCapacity
Indicates the greatest number of passengers that an entity is designed or allowed to carry at one time.
-
C.
weightLimitInPounds
Indicates the maximum allowable weight for something, expressed in pounds.
-
D.
leoPayloadCapacity
Indicates the maximum payload mass or capacity that can be delivered to Low Earth Orbit (LEO) in the context of a launch vehicle or space mission.
-
E.
cargoCapacityFeature
Indicates that an entity has a feature specifying how much cargo it can carry or accommodate.
- 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_69c68828b26c819090fe9df7612bbc27 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d30ded6481908fd64611607c610e |
completed | March 27, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69c6d09bb4f881909bf20c188cb3e8e1 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:16 p.m.