Triple
T31336862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | L-twin |
E799197
|
entity |
| Predicate | isCommonInVehicleType |
P175467
|
FINISHED |
| Object | motorcycle |
—
|
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: motorcycle | Statement: [L-twin, isCommonInVehicleType, motorcycle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommonInVehicleType Context triple: [L-twin, isCommonInVehicleType, motorcycle]
-
A.
appliedToVehicleType
Indicates that something (such as a rule, restriction, or condition) is specifically applicable to a particular type or category of vehicle.
-
B.
usedByVehicleType
Indicates that something (such as a resource, component, or facility) is utilized or operated by a specific type or category of vehicle.
-
C.
hasVehicularUse
Indicates that something is used for, intended for, or associated with operation by vehicles or vehicular traffic.
-
D.
isTransportationType
Indicates that one entity functions as a mode or category of transportation for the other entity.
-
E.
usedInCar
Indicates that something is utilized as a component, feature, or element within a car.
- 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_69f224e3f6ac8190a13488516abca7c9 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6d210fc80819091ed8961aa2cddfb |
completed | May 3, 2026, 4:41 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d16b79dc8190ab0d4657f2ef9a5b |
completed | May 3, 2026, 4:39 a.m. |
Created at: April 29, 2026, 9:16 p.m.