Triple
T33990106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow airports |
E871517
|
entity |
| Predicate | typicalFlightRange |
P13474
|
FINISHED |
| Object | domestic |
—
|
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: domestic | Statement: [Moscow airports, typicalFlightRange, domestic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFlightRange Context triple: [Moscow airports, typicalFlightRange, domestic]
-
A.
flightRangeFocus
Indicates that the relationship centers on the range or distance a flight can cover, emphasizing limitations or focus on how far the flight can travel.
-
B.
aircraftRangeCategory
Indicates the classification of an aircraft based on the distance it is capable of flying on a typical mission or with standard fuel capacity.
-
C.
maximumRangeNauticalMiles
Indicates the greatest distance, measured in nautical miles, that something can travel or operate under specified conditions.
-
D.
maximumFlightDuration
Indicates the longest allowable or observed time period that a flight can continuously operate.
-
E.
typicalRange
chosen
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
- 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_69f3499e964c8190b674b03f6f791b4b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:50 a.m.