Triple
T29367348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barrovian metamorphism |
E744754
|
entity |
| Predicate | indexMineralSequenceIncludes |
P45236
|
FINISHED |
| Object | chlorite |
—
|
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: chlorite | Statement: [Barrovian metamorphism, indexMineralSequenceIncludes, chlorite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indexMineralSequenceIncludes Context triple: [Barrovian metamorphism, indexMineralSequenceIncludes, chlorite]
-
A.
hasMineralClass
Indicates that an entity is associated with, or categorized under, a particular mineral classification.
-
B.
hasMineral
chosen
Indicates that one entity contains, includes, or is composed of a specified mineral.
-
C.
hasMineralFeature
Indicates that one entity possesses, contains, or is characterized by a specific mineral-related feature or attribute.
-
D.
typeOfMineralsCovered
Indicates that one entity specifies or lists the kinds or categories of minerals that are included, addressed, or affected by another entity.
-
E.
isMineralRich
Indicates that a location or substance contains a high concentration or abundance of minerals.
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6698dd5a88190a090841574689d0b |
completed | May 2, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 2:24 p.m.