Triple
T33839549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 15 landing site |
E867321
|
entity |
| Predicate | sampleCollectionMass |
P54856
|
FINISHED |
| Object | about 77 kg of lunar 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: about 77 kg of lunar samples | Statement: [Apollo 15 landing site, sampleCollectionMass, about 77 kg of lunar samples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sampleCollectionMass Context triple: [Apollo 15 landing site, sampleCollectionMass, about 77 kg of lunar samples]
-
A.
sampleCollectionMedium
Indicates the physical medium, material, or device used to collect or hold a sample during the sampling process.
-
B.
returnedSampleMass
chosen
Indicates that a specified amount of mass was brought back or retrieved as a sample from a source or mission.
-
C.
sampleCollected
Indicates that a sample has been obtained or gathered from a source as part of a collection process.
-
D.
obtainsMassVia
Indicates that an entity acquires its mass through a specified process, mechanism, or interaction.
-
E.
hasMasses
Indicates that one entity possesses or is associated with one or more masses (quantities of matter).
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:47 a.m.