Triple
T37442719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ranger lunar probe program |
E930462
|
entity |
| Predicate | Ranger9_impactSite |
P124734
|
FINISHED |
| Object | Alphonsus crater region |
—
|
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: Alphonsus crater region | Statement: [Ranger lunar probe program, Ranger9_impactSite, Alphonsus crater region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Ranger9_impactSite Context triple: [Ranger lunar probe program, Ranger9_impactSite, Alphonsus crater region]
-
A.
Ranger9_impactDate
Indicates the date on which the Ranger 9 mission (or spacecraft) impacted its target body.
-
B.
Ranger8_impactDate
Indicates the date on which the Ranger 8 spacecraft impacted its target (e.g., the Moon or another celestial body).
-
C.
Ranger7_impactDate
Indicates the date on which the Ranger 7 mission impacted its target (e.g., the lunar surface).
-
D.
actualImpactSite
chosen
Indicates the location where an impact actually occurred, as opposed to a predicted, intended, or nominal impact site.
-
E.
impactPosition
Indicates the specific location or coordinates at which an impact or collision occurs between entities.
- 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_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.