Triple
T33839911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lunar Sample 15415 |
E867330
|
entity |
| Predicate | collectedOnExtravehicularActivity |
P193430
|
FINISHED |
| Object | Apollo 15 EVA 2 |
—
|
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: Apollo 15 EVA 2 | Statement: [Lunar Sample 15415, collectedOnExtravehicularActivity, Apollo 15 EVA 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectedOnExtravehicularActivity Context triple: [Lunar Sample 15415, collectedOnExtravehicularActivity, Apollo 15 EVA 2]
-
A.
collectedOnCelestialBody
Indicates that something (typically a sample or data) was gathered or obtained while located on a specific celestial body.
-
B.
usedByAstronaut
Indicates that something is utilized or operated by an astronaut.
-
C.
crewEVAHours
Indicates the total number of hours that crew members spend performing extravehicular activities (spacewalks) outside their vehicle or habitat.
-
D.
dateOfMoonLandingEVA
Indicates the specific calendar date on which a particular extravehicular activity (EVA) occurred during a Moon landing mission.
-
E.
spacewalkOccurredOnMission
Indicates that a spacewalk took place during a specific space mission.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
| PDg | Predicate description generation | batch_69fd474a71648190b6b6ae4991db81b1 |
completed | May 8, 2026, 2:15 a.m. |
Created at: May 1, 2026, 1:47 a.m.