Triple
T30062223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sikorsky X |
E763920
|
entity |
| Predicate | locatedOnLunarFeature |
P47353
|
FINISHED |
| Object | lunar far side |
—
|
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: lunar far side | Statement: [Sikorsky X, locatedOnLunarFeature, lunar far side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnLunarFeature Context triple: [Sikorsky X, locatedOnLunarFeature, lunar far side]
-
A.
locatedOnSideOfMoon
chosen
Indicates that one entity is situated on a specific side or hemisphere of the Moon relative to another reference frame or viewpoint.
-
B.
locatedInCrater
Indicates that one entity is situated within the boundaries of a specific crater.
-
C.
isOnMoonOf
Indicates that one entity is located on, or positioned upon the surface of, a natural satellite (moon) that orbits another specified celestial body.
-
D.
lunarLandingRegion
Indicates the geographic region on the Moon where a spacecraft or mission has landed.
-
E.
lunarLandingSiteDetail
Indicates the specific characteristics or contextual information associated with a lunar landing site.
- 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a0091ad8b8c8190b0f00a3358e59bc1 |
completed | May 10, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_6a008f2813ec81909a54c2dfa5c75dc7 |
completed | May 10, 2026, 1:59 p.m. |
Created at: April 29, 2026, 6:58 p.m.