Triple
T364000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo program |
E7918
|
entity |
| Predicate | scientificOutcome |
P374
|
FINISHED |
| Object | returned lunar rock and soil 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: returned lunar rock and soil samples | Statement: [Apollo program, scientificOutcome, returned lunar rock and soil samples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scientificOutcome Context triple: [Apollo program, scientificOutcome, returned lunar rock and soil samples]
-
A.
researchArm
Indicates that an entity is a specific study group or treatment arm within a research or clinical trial design.
-
B.
scienceGoals
Indicates the objectives or intended outcomes that guide and justify a scientific activity, project, or investigation.
-
C.
result
chosen
Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
-
D.
scientificConsensus
Indicates that there is broad agreement among qualified experts or authoritative sources that a particular claim, finding, or theory is valid.
-
E.
researchProgram
Indicates that an entity is engaged in, associated with, or part of a structured research initiative or program.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebd1016481909b8ba3b047a47145 |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95dbb208190b277fc5352a4ee84 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.