Triple
T17928808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 35 |
E448269
|
entity |
| Predicate | hasReferenceSystem |
P94113
|
FINISHED |
| Object | magnetic north |
—
|
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 north | Statement: [Runway 35, hasReferenceSystem, magnetic north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReferenceSystem Context triple: [Runway 35, hasReferenceSystem, magnetic north]
-
A.
hasProjectionSystem
Indicates that one entity uses or is defined by a particular coordinate or map projection system associated with another entity.
-
B.
isReferencePointFor
Indicates that one entity serves as a positional or conceptual basis used to locate, measure, or interpret another entity.
-
C.
hasSummitCoordinateSystem
Indicates that a summit or peak is associated with a specific coordinate system used to define its geographic position.
-
D.
coordinateReferenceSystemType
chosen
Indicates the specific kind or category of coordinate reference system (e.g., geographic, projected, vertical) associated with a spatial dataset or geometry.
-
E.
hasReferenceID
Indicates that an entity is associated with a specific reference identifier used to uniquely track or distinguish it.
- 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_69d8b9f79d14819095540856928f0e25 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a5511a408190973cf5fa1f286a26 |
completed | April 19, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69e3f8e713d481908b4a126258c18b63 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:20 a.m.