Triple
T33839559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 15 landing site |
E867321
|
entity |
| Predicate | notableRockSample |
P206695
|
FINISHED |
| Object | Genesis Rock |
E247687
|
NE 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: Genesis Rock | Statement: [Apollo 15 landing site, notableRockSample, Genesis Rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableRockSample Context triple: [Apollo 15 landing site, notableRockSample, Genesis Rock]
-
A.
notableRockFormation
Indicates that one entity is a rock formation that is especially remarkable, distinctive, or well-known in relation to the other entity.
-
B.
notableQuarry
Indicates that an entity is a quarry that is particularly significant, well-known, or noteworthy in some context.
-
C.
notableCave
Indicates that the subject is a cave that is notable or significant in some recognized way.
-
D.
hasGeologicalSignificanceVia
Indicates that something possesses geological significance specifically through, or as established by, a particular mediating factor, process, or evidence.
-
E.
hasRockType
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
- F. None of above. chosen
Provenance (5 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_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a366ead654c8190abe9721f483eacfd |
completed | June 20, 2026, 10:42 a.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037e07fe4481909ca21eae7a941ee7 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 1, 2026, 1:47 a.m.