Triple
T27674111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Base 25 |
E697734
|
entity |
| Predicate | launchAzimuthsInclude |
P32751
|
FINISHED |
| Object | southward trajectories |
—
|
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: southward trajectories | Statement: [Base 25, launchAzimuthsInclude, southward trajectories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchAzimuthsInclude Context triple: [Base 25, launchAzimuthsInclude, southward trajectories]
-
A.
launchAzimuth
Indicates the directional angle or bearing along which a launch (such as a rocket or missile) is initiated relative to a reference direction.
-
B.
azimuthCoverage
chosen
Indicates the range or extent of directional angles (azimuths) over which something, such as a sensor or system, provides coverage or operates.
-
C.
azimuthAccuracy
Indicates the degree of precision or allowable error in the measured or specified azimuth angle between entities.
-
D.
launchesFromSilo
Indicates that something is launched starting from a silo as its point of origin.
-
E.
launchesFrom
Indicates that an object or agent initiates its movement, operation, or departure starting at a specified location or source.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 27, 2026, 2:42 p.m.