Triple
T31238519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duratec |
E796492
|
entity |
| Predicate | hasDisplacementRange |
P52251
|
FINISHED |
| Object | 1.25 L to 3.0 L |
—
|
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: 1.25 L to 3.0 L | Statement: [Duratec, hasDisplacementRange, 1.25 L to 3.0 L]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDisplacementRange Context triple: [Duratec, hasDisplacementRange, 1.25 L to 3.0 L]
-
A.
hasDisplacement
Indicates a relationship where an entity experiences or is assigned a change in position or location from an initial point to a final point.
-
B.
displacementRange
chosen
Indicates the minimum and maximum extent of positional change or movement that an entity can undergo or exhibits.
-
C.
hasMaxDisplacement
Indicates the maximum distance or extent to which something can move or be displaced from its original position.
-
D.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
E.
hasDepthRange
Indicates that an entity is associated with a minimum and maximum depth within which it occurs, applies, or is valid.
- 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_69f224db69ac81909a370adad6a7ac7c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fdee770af48190aca2670db50f8b49 |
completed | May 8, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69fdecec98a08190a357d816dc2a6dbe |
completed | May 8, 2026, 2:02 p.m. |
Created at: April 29, 2026, 9:11 p.m.