Triple
T35906041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fuzuli region |
E1038473
|
entity |
| Predicate | hasMineContamination |
P98276
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Fuzuli region, hasMineContamination, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMineContamination Context triple: [Fuzuli region, hasMineContamination, yes]
-
A.
containsContaminant
Indicates that one entity includes, holds, or is tainted by an unwanted or harmful contaminating substance or element.
-
B.
hasPollutionIssue
chosen
Indicates that an entity is affected by, associated with, or characterized by a pollution-related problem or concern.
-
C.
isInfestedWith
Indicates that one entity is overrun, occupied, or contaminated by another, typically unwanted, organism or agent.
-
D.
hasNotableMine
Indicates that an entity possesses or is associated with a mine considered significant or noteworthy in some context.
-
E.
hasMineralContent
Indicates that an entity contains or is characterized by a specific type or amount of mineral content.
- 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: May 3, 2026, 4:07 p.m.