Triple
T10550661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Class G airspace |
E248937
|
entity |
| Predicate | collisionAvoidanceMethod |
P82770
|
FINISHED |
| Object | see-and-avoid principle |
—
|
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: see-and-avoid principle | Statement: [Class G airspace, collisionAvoidanceMethod, see-and-avoid principle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collisionAvoidanceMethod Context triple: [Class G airspace, collisionAvoidanceMethod, see-and-avoid principle]
-
A.
collisionDetectionMethod
Indicates the technique or algorithm used to determine whether two or more entities come into contact or intersect.
-
B.
seeksToAvoid
Indicates an entity’s intention or effort to stay away from, prevent, or not experience another entity or situation.
-
C.
collisionHandling
Indicates how interactions between objects are managed when they come into contact or attempt to occupy the same space.
-
D.
avoidanceStrategy
chosen
Indicates a relationship where one entity deliberately takes actions or adopts behaviors to evade, minimize, or escape interaction, contact, or confrontation with another entity or situation.
-
E.
collisionSystem
Indicates a physical interaction where two or more entities impact or collide with each other within a defined system or environment.
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d52710869c81909b6db1a190825bad |
completed | April 7, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69d518fa0b4081909bffc936d78bd77b |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:34 p.m.