Triple
T10454706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Descartes Highlands |
E246520
|
entity |
| Predicate | sampleReturn |
P92737
|
FINISHED |
| Object | lunar highland rocks |
—
|
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: lunar highland rocks | Statement: [Descartes Highlands, sampleReturn, lunar highland rocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sampleReturn Context triple: [Descartes Highlands, sampleReturn, lunar highland rocks]
-
A.
returnService
Indicates a relationship where a service that was previously provided is being sent back, reversed, or requested to be undone or refunded.
-
B.
returnsAs
Indicates that one entity goes back to or resumes a previous state, location, role, or condition associated with another entity.
-
C.
returns
Indicates that one entity gives or sends something back to another entity, often as a result or outcome of a process or action.
-
D.
postSampleReturnTarget
chosen
Indicates that an entity is designated as the target location or object for returning a sample after it has been collected or processed.
-
E.
postSampleReturnMission
Indicates a relationship where an event, action, or state occurs after the completion of a sample-return 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe47fee48190b38ec0466ff0165a |
completed | April 7, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_69d4fb7d353c8190a73f439a956c7606 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:17 p.m.