Triple
T17318915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Sandy Strait |
E420502
|
entity |
| Predicate | RamsarListingYear |
P6137
|
FINISHED |
| Object | 1999 |
—
|
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: 1999 | Statement: [Great Sandy Strait, RamsarListingYear, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RamsarListingYear Context triple: [Great Sandy Strait, RamsarListingYear, 1999]
-
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.
RamsarSiteNumber
Indicates that an entity is designated as a Ramsar wetland site and specifies its unique identification number within the Ramsar Convention registry.
-
C.
RamsarSiteIn
Indicates that a wetland area has been designated as a Ramsar site and is located within a specified geographic or administrative region.
-
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.
RamsarSiteName
Indicates that a location is designated as a Ramsar wetland site and specifies the official name of that 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_69d889d22b848190a4663d0b8f8f76e7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4399f84a881908dd99ecd7cc02708 |
completed | April 19, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69e3b01b9d1c8190a406dd941c9b11a1 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:43 a.m.