Triple
T33839886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 15 anorthosite suite |
E867329
|
entity |
| Predicate | includesSample |
P190475
|
FINISHED |
| Object | lunar sample 15415 |
—
|
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: lunar sample 15415 | Statement: [Apollo 15 anorthosite suite, includesSample, lunar sample 15415]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesSample Context triple: [Apollo 15 anorthosite suite, includesSample, lunar sample 15415]
-
A.
includesStandard
Indicates that one entity contains, incorporates, or makes use of a particular standard as part of its definition, implementation, or specification.
-
B.
includesExamplesSuchAs
Indicates that one entity provides specific instances or samples that illustrate or clarify another entity.
-
C.
includedSingle
chosen
Indicates that one specific, individual item is contained within or made part of another set, group, or collection.
-
D.
includesPackage
Indicates that one entity contains or comes bundled with a particular package as part of its composition or offering.
-
E.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
- 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_6a036b0755888190a68a673664f0ea46 |
completed | May 12, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_6a036228676c8190aac9c90f7d8cedf7 |
completed | May 12, 2026, 5:23 p.m. |
Created at: May 1, 2026, 1:47 a.m.