Triple
T13203282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MGY |
E314293
|
entity |
| Predicate | distressSignalApproximateCoordinates |
P81574
|
FINISHED |
| Object | 41°43′N 49°56′W |
—
|
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: 41°43′N 49°56′W | Statement: [MGY, distressSignalApproximateCoordinates, 41°43′N 49°56′W]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distressSignalApproximateCoordinates Context triple: [MGY, distressSignalApproximateCoordinates, 41°43′N 49°56′W]
-
A.
satelliteLocation
Indicates that one entity is located in orbit around or positioned relative to another celestial body or reference point, as a satellite.
-
B.
coordinatesSpacecraft
Indicates overseeing and directing the movement and positioning of a spacecraft within its operational space.
-
C.
coordinatesMissionControlFor
Indicates that one entity is responsible for organizing, directing, and managing mission control operations for another entity.
-
D.
positionRelativeToEarth
chosen
Indicates the spatial position or orientation of an entity in relation to the Earth as a reference frame.
-
E.
approximateAircraftLost
Indicates an estimated or approximate number of aircraft that were lost in an event or operation.
- 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc6bc108190b5a6a265bf6e9fd4 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:17 p.m.