Triple
T38125551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falcon 9 Flight 1 |
E952056
|
entity |
| Predicate | launchAzimuthApproximate |
P21241
|
FINISHED |
| Object | 45 degrees |
—
|
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: 45 degrees | Statement: [Falcon 9 Flight 1, launchAzimuthApproximate, 45 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchAzimuthApproximate Context triple: [Falcon 9 Flight 1, launchAzimuthApproximate, 45 degrees]
-
A.
launchAzimuth
chosen
Indicates the directional angle or bearing along which a launch (such as a rocket or missile) is initiated relative to a reference direction.
-
B.
azimuthAccuracy
Indicates the degree of precision or allowable error in the measured or specified azimuth angle between entities.
-
C.
azimuthCoverage
Indicates the range or extent of directional angles (azimuths) over which something, such as a sensor or system, provides coverage or operates.
-
D.
aimedAtElevation
Indicates that an action or object is directed toward a specific vertical angle or height above a reference level.
-
E.
azimuthalAngleRepresents
Indicates that one entity specifies or encodes the azimuthal angle value associated with another entity or reference frame.
- 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: May 3, 2026, 4:21 p.m.