Triple
T33839902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 15 anorthosite suite |
E867329
|
entity |
| Predicate | sampleReturnType |
P179728
|
FINISHED |
| Object | manned lunar surface collection |
—
|
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: manned lunar surface collection | Statement: [Apollo 15 anorthosite suite, sampleReturnType, manned lunar surface collection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sampleReturnType Context triple: [Apollo 15 anorthosite suite, sampleReturnType, manned lunar surface collection]
-
A.
sampleType
Indicates the classification or category of a sample in relation to a broader set of samples or experimental conditions.
-
B.
sampleReturnBody
Indicates that an entity returns a sample item or specimen to another entity or location.
-
C.
resultType
Indicates the type or category of outcome that is produced by a given process, action, or operation.
-
D.
samplingType
Indicates the method or strategy used to select samples from a larger set or population.
-
E.
bodyReturnType
Indicates the data type of the value that a method or function returns in its response body.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
| PDg | Predicate description generation | batch_69f727bd39b081908457590c3ba9b745 |
completed | May 3, 2026, 10:47 a.m. |
Created at: May 1, 2026, 1:47 a.m.