Triple
T9370788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ducati Hypermotard |
E225523
|
entity |
| Predicate | typicalDisplacementRange |
P52251
|
FINISHED |
| Object | 800–1100 cc |
—
|
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: 800–1100 cc | Statement: [Ducati Hypermotard, typicalDisplacementRange, 800–1100 cc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalDisplacementRange Context triple: [Ducati Hypermotard, typicalDisplacementRange, 800–1100 cc]
-
A.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
B.
displacementRange
chosen
Indicates the minimum and maximum extent of positional change or movement that an entity can undergo or exhibits.
-
C.
typicalTrackLengthRange
Indicates the usual minimum and maximum lengths that a track associated with something tends to fall between.
-
D.
typicalDimension
Indicates that one entity represents a standard or characteristic measurement (such as size, length, or capacity) typically associated with another entity.
-
E.
typicalLength
Indicates the usual or characteristic length associated with an entity or phenomenon.
- 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_69ca842cbddc819099d71ecec48cf9e5 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd5083cbb8819088e8cef26be1b380 |
completed | April 1, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69cc7a6abb8c81908c7a2f4ee92cc949 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:43 p.m.