Triple
T16691334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European human spaceflight programme |
E405598
|
entity |
| Predicate | futureGoal |
P6636
|
FINISHED |
| Object | support human missions to the Moon |
—
|
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: support human missions to the Moon | Statement: [European human spaceflight programme, futureGoal, support human missions to the Moon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: futureGoal Context triple: [European human spaceflight programme, futureGoal, support human missions to the Moon]
-
A.
laterGoal
Indicates that one goal occurs or is intended to be achieved after another goal in time.
-
B.
legacyGoal
Indicates that an entity has a long-term, enduring objective or impact it aims to leave behind beyond its immediate actions or existence.
-
C.
goalHorizon
Indicates the temporal or planning horizon within which a goal is intended to be pursued or achieved.
-
D.
goals
chosen
Indicates that an entity has objectives, targets, or desired outcomes it aims to achieve.
-
E.
laterSocietyGoal
Indicates that a society adopts or aims to achieve a particular goal at a later time or stage in its development.
- 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.