Triple
T34643547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surveyor 3 landing site |
E889633
|
entity |
| Predicate | sampleTypeReturned |
P179728
|
FINISHED |
| Object | spacecraft material 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: spacecraft material samples | Statement: [Surveyor 3 landing site, sampleTypeReturned, spacecraft material samples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sampleTypeReturned Context triple: [Surveyor 3 landing site, sampleTypeReturned, spacecraft material samples]
-
A.
sampleType
Indicates the classification or category of a sample in relation to a broader set of samples or experimental conditions.
-
B.
sampleReturnType
chosen
Indicates the type or category of value that a sample or sampling process is expected to produce or return.
-
C.
samplingType
Indicates the method or strategy used to select samples from a larger set or population.
-
D.
surfaceSampleReturnedBy
Indicates that a collected surface sample was physically returned by a specified mission, vehicle, or agent.
-
E.
returnedSamplesTo
Indicates that one entity has given back or delivered previously obtained samples to another entity.
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f728a345488190bd7e6751b09ac591 |
completed | May 3, 2026, 10:51 a.m. |
| PD | Predicate disambiguation | batch_69f7283ef2608190a7a85d7e7f5332c0 |
completed | May 3, 2026, 10:49 a.m. |
Created at: May 1, 2026, 2:04 a.m.