Triple
T3064019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lunar Gateway |
E62060
|
entity |
| Predicate | scientificUse |
P24615
|
FINISHED |
| Object | space environment research |
—
|
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: space environment research | Statement: [Lunar Gateway, scientificUse, space environment research]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scientificUse Context triple: [Lunar Gateway, scientificUse, space environment research]
-
A.
isScientific
Indicates that something pertains to or is based on systematic scientific methods, principles, or knowledge.
-
B.
scientificInstruments
Indicates that one entity is a scientific instrument used by, associated with, or relevant to another entity in the context of scientific measurement or research.
-
C.
hasResearchUse
chosen
Indicates that an entity is used for, or associated with, conducting research activities or purposes.
-
D.
primaryScienceUse
Indicates that something serves as the main or principal scientific purpose or application of an entity or resource.
-
E.
usedResearchFrom
Indicates that one entity based its work, findings, or outputs on research conducted or provided by another entity.
- 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_69ad85793e5c8190a358049bc4a98d8c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9ea2154c8190ab243feb77170a15 |
completed | March 8, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69ad9624b7a0819091d255614f5819ea |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.