Triple
T21252723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chagos Archipelago |
E523784
|
entity |
| Predicate | marineProtectedAreaYear |
P14276
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Chagos Archipelago, marineProtectedAreaYear, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marineProtectedAreaYear Context triple: [Chagos Archipelago, marineProtectedAreaYear, 2010]
-
A.
marineProtectedAreaDesignationYear
chosen
Indicates the year in which an area was formally designated as a marine protected area.
-
B.
marineProtectedArea
Indicates that an area of marine or coastal waters is designated and managed to conserve natural resources and biodiversity, often restricting certain human activities.
-
C.
marineProtectedAreaOf
Indicates that one entity is designated as a marine protected area that encompasses, is associated with, or provides protection for the other entity.
-
D.
establishedProtectedAreaYear
Indicates the year in which a protected area was officially established or designated.
-
E.
marineProtectedAreaManagingCountry
Indicates that a country is responsible for managing or overseeing a specific marine protected area.
- 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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7359f5b408190b951adddba83c97a |
completed | April 21, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:57 p.m.