Triple
T33839907
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lunar Sample 15415 |
E867330
|
entity |
| Predicate | collectedDuringMission |
P90250
|
FINISHED |
| Object | Apollo 15 |
—
|
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 | Statement: [Lunar Sample 15415, collectedDuringMission, Apollo 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectedDuringMission Context triple: [Lunar Sample 15415, collectedDuringMission, Apollo 15]
-
A.
sampledDuringMission
chosen
Indicates that one entity was collected or sampled in the course of a specific mission involving the other entity.
-
B.
collectedByMissionType
Indicates that something (such as data or samples) was gathered as part of a mission characterized by a specific mission type.
-
C.
sampledDuringMissionNumber
Indicates that a sample was collected or measured during a mission identified by a specific mission number.
-
D.
operatedOnMission
Indicates that an agent carried out or participated in the execution of a specific mission.
-
E.
usedByMission
Indicates that something (such as a resource, tool, or method) is utilized or employed in the execution of a particular mission.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: May 1, 2026, 1:47 a.m.