Triple
T28137623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dnieper‑Donets Basin |
E714251
|
entity |
| Predicate | hasSealRocks |
P134055
|
FINISHED |
| Object | evaporites |
—
|
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: evaporites | Statement: [Dnieper‑Donets Basin, hasSealRocks, evaporites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSealRocks Context triple: [Dnieper‑Donets Basin, hasSealRocks, evaporites]
-
A.
sealRocks
chosen
Indicates that one entity closes off or covers another entity using rocks as a barrier or sealing material.
-
B.
hasTribalSeal
Indicates that an entity bears, is marked with, or is officially associated with a specific tribal seal.
-
C.
hasRockType
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
D.
isSealOf
Indicates that one entity serves as the official seal, emblem, or stamp that authenticates, endorses, or formally represents another entity.
-
E.
usedSeal
Indicates that an entity has applied or employed a seal (e.g., for closure, authentication, or protection) on another entity.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: April 27, 2026, 9:51 p.m.