Triple
T24428695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mississippi Valley-Type lead-zinc district |
E615931
|
entity |
| Predicate | hasAlteration |
P144621
|
FINISHED |
| Object | dolomitization |
—
|
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: dolomitization | Statement: [Mississippi Valley-Type lead-zinc district, hasAlteration, dolomitization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlteration Context triple: [Mississippi Valley-Type lead-zinc district, hasAlteration, dolomitization]
-
A.
hasAlterationPeriod
Indicates that an entity is associated with a specific time span during which changes, modifications, or alterations may occur or are valid.
-
B.
alterationType
chosen
Indicates the specific kind or category of change or modification that has been applied to an entity or relationship.
-
C.
hasHumanModification
Indicates that an entity has been altered, influenced, or modified as a result of human activity or intervention.
-
D.
hasAminoAcidChange
Indicates that an entity (such as a protein or gene variant) involves or results in a specific change from one amino acid to another in its sequence.
-
E.
hasDesignChange
Indicates that an entity has undergone a modification or alteration to its original design.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296a983d88190904b559694363a19 |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:15 a.m.