Triple
T8921178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polesie nature reserves |
E212417
|
entity |
| Predicate | includesDesignation |
P974
|
FINISHED |
| Object | Ramsar sites |
—
|
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: Ramsar sites | Statement: [Polesie nature reserves, includesDesignation, Ramsar sites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesDesignation Context triple: [Polesie nature reserves, includesDesignation, Ramsar sites]
-
A.
associatedDesignation
Indicates that one entity is linked to or identified by a particular designation, title, or label connected with it.
-
B.
hasDesignation
chosen
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
-
C.
exampleDesignation
Indicates that one entity is identified or labeled as a representative or illustrative instance of another entity.
-
D.
hasDesignationBy
Indicates that one entity has been formally assigned or labeled with a specific designation by another entity.
-
E.
hasInternalDesignationFor
Indicates that one entity assigns or uses an internal label, code, or designation to refer to 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc665024f081909515e02e5f5b2221 |
completed | April 1, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:56 p.m.