Triple
T33839899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 15 anorthosite suite |
E867329
|
entity |
| Predicate | mineralogyFeature |
P125271
|
FINISHED |
| Object | high plagioclase content |
—
|
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: high plagioclase content | Statement: [Apollo 15 anorthosite suite, mineralogyFeature, high plagioclase content]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mineralogyFeature Context triple: [Apollo 15 anorthosite suite, mineralogyFeature, high plagioclase content]
-
A.
hasMineralFeature
chosen
Indicates that one entity possesses, contains, or is characterized by a specific mineral-related feature or attribute.
-
B.
mineralogy
Indicates the study or characterization of the mineral composition and properties associated with an entity.
-
C.
mineralGroup
Indicates that one entity is classified as a member or subtype of a particular mineral group defined by shared mineralogical characteristics.
-
D.
mineralFamily
Indicates that one mineral belongs to, or is classified within, the broader family or group represented by another mineral or mineral category.
-
E.
hasMineral
Indicates that one entity contains, includes, or is composed of a specified mineral.
- 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_69f7004e55988190a2d35d4a95a34610 |
completed | May 3, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.