Triple
T3115469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chevrolet Express (facelifted variants) |
E65051
|
entity |
| Predicate | offeredBodyLength |
P18065
|
FINISHED |
| Object | regular wheelbase |
—
|
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: regular wheelbase | Statement: [Chevrolet Express (facelifted variants), offeredBodyLength, regular wheelbase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredBodyLength Context triple: [Chevrolet Express (facelifted variants), offeredBodyLength, regular wheelbase]
-
A.
properLengthMeasuredIn
Indicates that the proper (intrinsic or rest-frame) length of an entity is expressed using a specified unit of measurement.
-
B.
typicalLength
chosen
Indicates the usual or characteristic length associated with an entity or phenomenon.
-
C.
bodySize
Indicates the relative physical magnitude or scale of an entity’s body, such as how large or small it is.
-
D.
lengthVariesBy
Indicates that the length of one entity changes or differs depending on another specified factor or condition.
-
E.
length
Indicates a measurement relationship where a value specifies how long something is from one end to the other.
- 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_69ad857fcc088190b0c4d45a5cde6f61 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada4e40bc48190b9b17c706a2450d5 |
completed | March 8, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_69ad9df455088190940ad04419772dc8 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.