Triple
T9837409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taurus–Littrow valley |
E239137
|
entity |
| Predicate | sampledDuringMission |
P90250
|
FINISHED |
| Object | Apollo 17 geological samples |
—
|
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: Apollo 17 geological samples | Statement: [Taurus–Littrow valley, sampledDuringMission, Apollo 17 geological samples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sampledDuringMission Context triple: [Taurus–Littrow valley, sampledDuringMission, Apollo 17 geological samples]
-
A.
observedByMission
Indicates that an event, object, or phenomenon was detected, recorded, or monitored by a specific mission.
-
B.
performedMission
Indicates that an agent has carried out or completed a specific mission or task.
-
C.
usedByMission
Indicates that something (such as a resource, tool, or method) is utilized or employed in the execution of a particular mission.
-
D.
isTargetOfMission
Indicates that an entity is the intended objective or focus of a particular mission or operation.
-
E.
removedDuringMission
Indicates that an entity was taken away, detached, or eliminated while a mission or operation was in progress.
- 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb347ff4c81908c312548a25bae71 |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06abc9248190a506b64e9c516d03 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:33 p.m.