Triple
T2849427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artemis III |
E63055
|
entity |
| Predicate | spaceSuitSystem |
P43405
|
FINISHED |
| Object | next-generation lunar EVA suits |
—
|
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: next-generation lunar EVA suits | Statement: [Artemis III, spaceSuitSystem, next-generation lunar EVA suits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spaceSuitSystem Context triple: [Artemis III, spaceSuitSystem, next-generation lunar EVA suits]
-
A.
servicedSpacecraft
Indicates that one entity has performed maintenance or support operations on a spacecraft.
-
B.
missionPatchDesigner
Indicates that one entity is the designer or creator of the mission patch associated with another entity (typically a space mission).
-
C.
hostSpacecraft
Indicates that one entity serves as the platform or carrier on which another spacecraft is mounted, accommodated, or operated.
-
D.
spacewalks
Indicates that an astronaut performs activities outside a spacecraft in open space, typically while wearing a spacesuit and tethered or otherwise supported.
-
E.
attachedToSpaceStation
Indicates that an object is physically connected or secured to a space station.
- F. None of above. chosen
Provenance (4 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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf41ac24819087c5b72e3b84117c |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd0e86808190bcefffafbd3cd441 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde2cdcc48190827195d3ae70aa19 |
completed | March 7, 2026, 8:13 a.m. |
Created at: March 6, 2026, 10:02 p.m.