Triple
T16180460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota Tacoma |
E392669
|
entity |
| Predicate | towingCapacityRange |
P25831
|
FINISHED |
| Object | approximately 3,500–6,800 lb depending on configuration |
—
|
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 3,500–6,800 lb depending on configuration | Statement: [Toyota Tacoma, towingCapacityRange, approximately 3,500–6,800 lb depending on configuration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: towingCapacityRange Context triple: [Toyota Tacoma, towingCapacityRange, approximately 3,500–6,800 lb depending on configuration]
-
A.
towingCapability
chosen
Indicates the maximum load or object weight that one entity is able to pull or tow.
-
B.
typicalTruckWeightRange
Indicates the usual minimum-to-maximum weight interval that trucks of a given type or category are expected to fall within.
-
C.
announcedGrossVehicleWeightRating
Indicates that an entity has a specified gross vehicle weight rating that has been formally announced or declared.
-
D.
cargoCapacityFeature
Indicates that an entity has a feature specifying how much cargo it can carry or accommodate.
-
E.
powerRange
Indicates the range of power values within which an entity operates, applies, or is considered valid.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2205c92b48190b7125dbbcff3662e |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.