Triple
T17179077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noachian |
E416933
|
entity |
| Predicate | mineralAssociation |
P125271
|
FINISHED |
| Object | phyllosilicate-rich terrains |
—
|
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: phyllosilicate-rich terrains | Statement: [Noachian, mineralAssociation, phyllosilicate-rich terrains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mineralAssociation Context triple: [Noachian, mineralAssociation, phyllosilicate-rich terrains]
-
A.
mineralGroup
Indicates that one entity is classified as a member or subtype of a particular mineral group defined by shared mineralogical characteristics.
-
B.
elementalAssociation
Indicates an association where one entity is linked or related to a particular element or elemental property (such as fire, water, earth, or air).
-
C.
hasMineral
Indicates that one entity contains, includes, or is composed of a specified mineral.
-
D.
hasMineralFeature
chosen
Indicates that one entity possesses, contains, or is characterized by a specific mineral-related feature or attribute.
-
E.
mineralizationType
Indicates the specific kind or style of mineral deposition or ore-forming process characterizing a mineralized occurrence or deposit.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3fc0f9a288190b0ddfb673bd8e84b |
completed | April 18, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e383141ae0819096acd71683637cbc |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.