Triple
T9940768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macquarie Island |
E194073
|
entity |
| Predicate | importantBirdArea |
P38862
|
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: [Macquarie Island, importantBirdArea, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importantBirdArea Context triple: [Macquarie Island, importantBirdArea, yes]
-
A.
recognizedAsImportantBirdArea
chosen
Indicates that a location has been officially designated as an Important Bird Area due to its significance for bird conservation.
-
B.
partOfRamsarSite
Indicates that one entity is a component or area included within a designated Ramsar wetland site.
-
C.
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.
-
D.
hasBiodiversitySignificance
Indicates that something possesses ecological importance due to the variety, rarity, or conservation value of the species and habitats it supports.
-
E.
hasMigratoryBirdUse
Indicates that an entity is used, visited, or relied upon by migratory birds, such as for feeding, resting, or breeding during migration.
- 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_69ca82e409348190a393777356b80a2a |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb60f4ffc8190bfe916bb4a7bf5c5 |
completed | April 2, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9428cc81909b4b4938566d78a7 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:44 p.m.