Triple
T2864343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artemis IV |
E63401
|
entity |
| Predicate | programGoalSupport |
P39887
|
FINISHED |
| Object | long-term lunar exploration |
—
|
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: long-term lunar exploration | Statement: [Artemis IV, programGoalSupport, long-term lunar exploration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programGoalSupport Context triple: [Artemis IV, programGoalSupport, long-term lunar exploration]
-
A.
supportGoal
chosen
Indicates that one entity actively helps, promotes, or contributes to the achievement of another entity’s goal.
-
B.
strategicGoal
Indicates that one entity represents a long-term objective or desired outcome that another entity is intentionally aiming to achieve or align actions toward.
-
C.
statedAsGoalFor
Indicates that something has been explicitly declared or identified as a goal for a particular entity or context.
-
D.
normativeGoal
Indicates that one entity is a desired or prescribed objective, standard, or end state that another entity ought to pursue or realize.
-
E.
goals
Indicates that an entity has objectives, targets, or desired outcomes it aims to achieve.
- 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_69ab4c42fb8c8190b36e161d47c03b81 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdfb853908190aa2fd492e9fa5e87 |
completed | March 7, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69abdd123ec48190af50a1859aea50b7 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.