Triple
T37442733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ranger lunar probe program |
E930462
|
entity |
| Predicate | laterMissionsOutcome |
P21239
|
FINISHED |
| Object | successful lunar imaging and impact |
—
|
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: successful lunar imaging and impact | Statement: [Ranger lunar probe program, laterMissionsOutcome, successful lunar imaging and impact]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterMissionsOutcome Context triple: [Ranger lunar probe program, laterMissionsOutcome, successful lunar imaging and impact]
-
A.
laterPrimaryMission
Indicates that one mission occurs after another mission in the sequence of primary missions.
-
B.
notableSuccessorMission
Indicates that one mission is a particularly prominent or significant successor to another mission in a sequence or lineage of related missions.
-
C.
nextMission
Indicates that one mission directly follows another in a planned or chronological sequence.
-
D.
missionOutcome
chosen
Indicates the result or consequence of a mission, specifying whether and how the mission’s objectives were achieved or failed.
-
E.
missionEnd
Indicates that a mission has concluded or reached its final state or outcome.
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a011d76f3f88190be3d7c9eb0552f34 |
completed | May 11, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_6a011cce684881909dd15776bb77a6e0 |
completed | May 11, 2026, 12:03 a.m. |
Created at: May 3, 2026, 4:17 p.m.