Triple
T21193933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeep CJ-6 |
E522278
|
entity |
| Predicate | wheelbaseExtension |
P25832
|
FINISHED |
| Object | approximately 20 inches longer than CJ-5 |
—
|
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 20 inches longer than CJ-5 | Statement: [Jeep CJ-6, wheelbaseExtension, approximately 20 inches longer than CJ-5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wheelbaseExtension Context triple: [Jeep CJ-6, wheelbaseExtension, approximately 20 inches longer than CJ-5]
-
A.
wheelbase
Indicates the distance between the centers of the front and rear wheels of a vehicle.
-
B.
wheelbaseVariantOf
chosen
Indicates a relationship where one vehicle’s wheelbase configuration is a variant or modified version of another vehicle’s wheelbase.
-
C.
wheelbaseClass
Indicates the classification of a vehicle based on the length or category of its wheelbase.
-
D.
wheelHeightApprox
Indicates that the height of a wheel is approximately equal to a specified value or to the height of another wheel.
-
E.
supportsWheelbaseVariants
Indicates that one entity is compatible with or designed to accommodate multiple wheelbase length variants of another 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73339aaa081909d9009c58c386422 |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6094e3c81909ee9699e00d371f7 |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:08 p.m.