Triple
T7311137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Alexandrina |
E168091
|
entity |
| Predicate | RamsarSiteDesignationYear |
P6137
|
FINISHED |
| Object | 1985 |
—
|
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: 1985 | Statement: [Lake Alexandrina, RamsarSiteDesignationYear, 1985]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RamsarSiteDesignationYear Context triple: [Lake Alexandrina, RamsarSiteDesignationYear, 1985]
-
A.
RamsarSiteSince
chosen
Indicates that a location has held the status of a Ramsar wetland site since a specified date or point in time.
-
B.
RamsarSiteIn
Indicates that a wetland area has been designated as a Ramsar site and is located within a specified geographic or administrative region.
-
C.
RamsarSiteNumber
Indicates that an entity is designated as a Ramsar wetland site and specifies its unique identification number within the Ramsar Convention registry.
-
D.
RamsarSite
Indicates that a wetland has been designated as a Ramsar Site, meaning it is recognized under the Ramsar Convention as a wetland of international importance.
-
E.
partOfRamsarSite
Indicates that one entity is a component or area included within a designated Ramsar wetland site.
- 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_69c6888d8e3c81909db79714903baf31 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebff866081909916796d1b72aee8 |
completed | March 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:02 p.m.