Triple
T32599875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shorty crater |
E833335
|
entity |
| Predicate | sampleCollectedDuring |
P127405
|
FINISHED |
| Object | Apollo 17 geological fieldwork |
—
|
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 fieldwork | Statement: [Shorty crater, sampleCollectedDuring, Apollo 17 geological fieldwork]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sampleCollectedDuring Context triple: [Shorty crater, sampleCollectedDuring, Apollo 17 geological fieldwork]
-
A.
sampleCollected
chosen
Indicates that a sample has been obtained or gathered from a source as part of a collection process.
-
B.
dataCollectedAt
Indicates that some data was gathered or recorded at a specific time or place.
-
C.
dataCollectedOn
Indicates that certain data was gathered, recorded, or measured at a specific point in time or on a particular date.
-
D.
collectedWith
Indicates that one entity was gathered, acquired, or obtained together with another entity as part of the same collection event or process.
-
E.
sampleCollectionMedium
Indicates the physical medium, material, or device used to collect or hold a sample during the sampling process.
- 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_69f3492ab63c8190aec24d5003b47c29 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:05 a.m.