Triple
T998936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saab 9-4X |
E21557
|
entity |
| Predicate | curbWeightRange |
P18770
|
FINISHED |
| Object | approximately 4300–4500 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 4300–4500 lb | Statement: [Saab 9-4X, curbWeightRange, approximately 4300–4500 lb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: curbWeightRange Context triple: [Saab 9-4X, curbWeightRange, approximately 4300–4500 lb]
-
A.
associatedVehicleWeightClass
Indicates the weight classification category that is linked or assigned to a particular vehicle.
-
B.
emptyWeight
chosen
Indicates the weight of an object or vehicle when it is empty, excluding any load, cargo, or passengers.
-
C.
announcedGrossVehicleWeightRating
Indicates that an entity has a specified gross vehicle weight rating that has been formally announced or declared.
-
D.
vehicleType
Indicates the specific kind or category of vehicle associated with an entity (e.g., car, bus, bicycle).
-
E.
availableEngineDisplacement
Indicates the range or specific values of engine displacement that are offered or applicable for a given entity.
- 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4e2ad9c81908a0f488d3f261fc3 |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2b057c48190b9e42df9246b3757 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.