Triple
T16691407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mu Center |
E405600
|
entity |
| Predicate | hasLaunchAzimuth |
P21241
|
FINISHED |
| Object | inclined orbits from Japan |
—
|
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: inclined orbits from Japan | Statement: [Mu Center, hasLaunchAzimuth, inclined orbits from Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaunchAzimuth Context triple: [Mu Center, hasLaunchAzimuth, inclined orbits from Japan]
-
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.
hasVerticalLaunchSystem
Indicates that one entity is equipped with a vertical launch system used to fire missiles or similar munitions vertically.
-
E.
orbitApogee
Indicates the point in an orbit where an orbiting body is farthest from the central body it revolves around.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ea99bac8190a6c559ed7b7d8ecd |
completed | April 18, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.