Triple
T10501738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genesis Rock |
E247687
|
entity |
| Predicate | missionSampleCollectionMethod |
P9384
|
FINISHED |
| Object | extravehicular activity (EVA) sampling |
—
|
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: extravehicular activity (EVA) sampling | Statement: [Genesis Rock, missionSampleCollectionMethod, extravehicular activity (EVA) sampling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionSampleCollectionMethod Context triple: [Genesis Rock, missionSampleCollectionMethod, extravehicular activity (EVA) sampling]
-
A.
collectedSpecimensIn
Indicates that an entity gathered or obtained specimens within a specified location or context.
-
B.
fieldOfCollection
Indicates the academic or subject area to which a collection or set of collected items belongs.
-
C.
collectedThrough
chosen
Indicates that something was obtained, gathered, or acquired by means of a specified process, method, or channel.
-
D.
dataCollectionLocation
Indicates the place or setting where data is gathered, recorded, or measured.
-
E.
collectedAs
Indicates that one entity has been gathered, acquired, or assembled as part of another entity, such as a collection, set, or group.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5099b797c8190a94803fa94eb6981 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8e24ac8190912c9f11b8bd3084 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:25 p.m.