Triple
T11926115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harley-Davidson V-Rod |
E283785
|
entity |
| Predicate | seatHeightApprox |
P102188
|
FINISHED |
| Object | 690 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: 690 mm | Statement: [Harley-Davidson V-Rod, seatHeightApprox, 690 mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seatHeightApprox Context triple: [Harley-Davidson V-Rod, seatHeightApprox, 690 mm]
-
A.
seatPitch
Indicates the distance between a seat and the seat directly in front of it, typically measuring legroom or spacing in a seating arrangement.
-
B.
seatStructure
Indicates that one entity serves as the structural or physical seating component or arrangement associated with another entity.
-
C.
seatRecline
Indicates that one entity adjusts or is capable of adjusting the backward tilt or reclining position of a seat relative to another entity or context.
-
D.
seatLocation
Indicates the spatial position or placement of a seat relative to a reference point or environment.
-
E.
hasSeatMaterial
Indicates that an entity’s seat is made of, or covered with, a specified material.
- F. None of above. chosen
Provenance (4 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_69d6ab2ce9c48190b5d39511b524f666 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8e8e3ff308190851ce656286bc67e |
completed | April 10, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3af0188190bfb22be5c97b3349 |
completed | April 10, 2026, 8:56 a.m. |
| PDg | Predicate description generation | batch_69d8d399d58c81908dab572aa82426d7 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 8, 2026, 9:45 p.m.