Triple
T30145685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | new generation MAN Lion’s City |
E766246
|
entity |
| Predicate | availableLength |
P160189
|
FINISHED |
| Object | approximately 10.5 m |
—
|
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 10.5 m | Statement: [new generation MAN Lion’s City, availableLength, approximately 10.5 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availableLength Context triple: [new generation MAN Lion’s City, availableLength, approximately 10.5 m]
-
A.
usableLength
chosen
Indicates the portion of an object’s total length that can actually be used for its intended function or purpose.
-
B.
extensionLength
Indicates the length or magnitude of an extension from a reference point or base object.
-
C.
availableWidth
Indicates the amount of horizontal space that is currently free or usable within a given context or container.
-
D.
properLengthMeasuredIn
Indicates that the proper (intrinsic or rest-frame) length of an entity is expressed using a specified unit of measurement.
-
E.
laneLength
Indicates the length or distance of a lane in a given context.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67e8b21048190b0fbccb10b2d3523 |
completed | May 2, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:18 p.m.