Triple
T27384094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 34 |
E691317
|
entity |
| Predicate | isAlignedToward |
P99988
|
FINISHED |
| Object | magnetic bearing 340° |
—
|
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: magnetic bearing 340° | Statement: [Runway 34, isAlignedToward, magnetic bearing 340°]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAlignedToward Context triple: [Runway 34, isAlignedToward, magnetic bearing 340°]
-
A.
originallyAlignedWith
Indicates that an entity was initially in agreement, support, or association with another entity or group, regardless of any later changes in stance or affiliation.
-
B.
rotationAlignedWith
chosen
Indicates that the orientation or rotational state of one entity is aligned or matched with that of another entity.
-
C.
laterAlignedWith
Indicates that one entity becomes aligned with or matches another entity at a later point in time, rather than initially.
-
D.
hasAlignment
Indicates that one entity shares or exhibits a particular orientation, stance, or compatibility in relation to another entity or standard.
-
E.
basedOnAlignmentOf
Indicates a relationship where one entity is determined, derived, or decided according to how closely it aligns with another entity’s position, orientation, or criteria.
- 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_69ef520386788190bc92cfcd97ebb67a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62cd2ceb481908cd9fae52a542206 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 12:23 p.m.