Triple
T1543587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 4 |
E32925
|
entity |
| Predicate | isRoundedFromHeadingRange |
P30197
|
FINISHED |
| Object | 035 to 044 degrees magnetic |
—
|
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: 035 to 044 degrees magnetic | Statement: [Runway 4, isRoundedFromHeadingRange, 035 to 044 degrees magnetic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRoundedFromHeadingRange Context triple: [Runway 4, isRoundedFromHeadingRange, 035 to 044 degrees magnetic]
-
A.
hasRound
Indicates that an entity possesses, includes, or is associated with a particular round (e.g., a round of an event, game, or process).
-
B.
hasProperRounds
Indicates that an entity is associated with rounds that meet specified standards or criteria for being considered proper or valid.
-
C.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
D.
hasRouteDirection
Indicates that a specified route is associated with a particular travel direction (e.g., inbound, outbound, northbound).
-
E.
roundel
Indicates that one entity bears, displays, or is marked with a circular emblem or symbol representing another entity.
- 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_69a885ed29088190a3c2d5a3d100c16e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa95c1a2948190a2b98469afec1a7d |
completed | March 6, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69a907b2453c8190a41f6b88c8217d1e |
completed | March 5, 2026, 4:33 a.m. |
| PDg | Predicate description generation | batch_69a93df847cc8190b6d011af33b34b40 |
completed | March 5, 2026, 8:25 a.m. |
Created at: March 4, 2026, 7:26 p.m.