Triple
T2529971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pontiac G6 |
E56132
|
entity |
| Predicate | lengthRange |
P266
|
FINISHED |
| Object | 189.0–189.2 in (4801–4806 mm) |
—
|
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: 189.0–189.2 in (4801–4806 mm) | Statement: [Pontiac G6, lengthRange, 189.0–189.2 in (4801–4806 mm)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lengthRange Context triple: [Pontiac G6, lengthRange, 189.0–189.2 in (4801–4806 mm)]
-
A.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
B.
rangeSize
Indicates the extent or magnitude of the range over which something applies, varies, or is distributed.
-
C.
length
chosen
Indicates a measurement relationship where a value specifies how long something is from one end to the other.
-
D.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
E.
rangeRestricted
Indicates that the relationship or action applies only within a specified, limited subset of a broader domain or scope.
- 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_69ab4a48e4f081908f1218d244608659 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd276930c8190bd46b52e06b7098e |
completed | March 7, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69abd0c2e34c8190a914d5c2afba147c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.