Triple
T34643534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surveyor 3 landing site |
E889633
|
entity |
| Predicate | hasSpacecraftWreckage |
P70310
|
FINISHED |
| Object | Surveyor 3 lander |
—
|
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: Surveyor 3 lander | Statement: [Surveyor 3 landing site, hasSpacecraftWreckage, Surveyor 3 lander]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpacecraftWreckage Context triple: [Surveyor 3 landing site, hasSpacecraftWreckage, Surveyor 3 lander]
-
A.
associatedWithSpacecraftImpact
chosen
Indicates that an entity is related to, involved in, or results from the impact of a spacecraft.
-
B.
spacecraftReentry
Indicates the event or process of a spacecraft returning from space and re-entering a planetary atmosphere.
-
C.
relatedSpacecraft
Indicates that there is an association or connection between two spacecraft, such as shared mission, design, origin, or operational relationship.
-
D.
ashesLaunchedIntoSpace
Indicates that a deceased person's ashes have been sent into outer space as part of a memorial or ceremonial launch.
-
E.
mentionsSpacecraft
Indicates that one entity makes reference to or discusses a particular spacecraft.
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
Created at: May 1, 2026, 2:04 a.m.