Triple
T13014279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tupolev Tu-330 |
E322503
|
entity |
| Predicate | intendedRangeClass |
P49736
|
FINISHED |
| Object | medium range |
—
|
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: medium range | Statement: [Tupolev Tu-330, intendedRangeClass, medium range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedRangeClass Context triple: [Tupolev Tu-330, intendedRangeClass, medium range]
-
A.
introducedRange
Indicates that an entity has brought a particular range (such as a span, interval, or set of values) into existence, use, or consideration.
-
B.
designedRange
chosen
Indicates the intended or specified range within which something is designed to operate or be effective.
-
C.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
D.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
E.
includesRange
Indicates that one entity’s span, interval, or range fully contains or covers the span, interval, or range of another entity.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97ecbb8f4819094d55eb07cb5ad97 |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:50 p.m.