Triple
T27929428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orion program |
E707936
|
entity |
| Predicate | plannedFirstCrewedLunarFlybyMission |
P170986
|
FINISHED |
| Object | Artemis II |
—
|
NE NERFINISHED |
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: Artemis II | Statement: [Orion program, plannedFirstCrewedLunarFlybyMission, Artemis II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedFirstCrewedLunarFlybyMission Context triple: [Orion program, plannedFirstCrewedLunarFlybyMission, Artemis II]
-
A.
plannedLunarMissionType
Indicates the type or category of a lunar mission that is planned or intended to be carried out.
-
B.
plannedFirstLunarLanding
Indicates that an entity is responsible for organizing or scheduling the earliest intended mission to land on the Moon.
-
C.
lunarMission
Indicates a mission or operation specifically directed toward exploring, studying, or traveling to the Moon.
-
D.
plannedFirstCrewedOrionFlight
Indicates that an event represents the first planned crewed flight using the Orion spacecraft.
-
E.
firstMannedLunarOrbitMission
Indicates that the subject is the first mission in which humans successfully entered into orbit around the Moon.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6984bb55c8190862eb8796868d188 |
completed | May 3, 2026, 12:35 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f6978ec27c8190a488e1f9c2566d38 |
completed | May 3, 2026, 12:32 a.m. |
Created at: April 27, 2026, 7:02 p.m.