Triple
T21348443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olango Island |
E526404
|
entity |
| Predicate | hasWildlifeSanctuaryArea |
P85576
|
FINISHED |
| Object | approximately 920 hectares |
—
|
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: approximately 920 hectares | Statement: [Olango Island, hasWildlifeSanctuaryArea, approximately 920 hectares]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWildlifeSanctuaryArea Context triple: [Olango Island, hasWildlifeSanctuaryArea, approximately 920 hectares]
-
A.
hasNearbyWildlifeRefuge
Indicates that something is located close to or in the vicinity of a designated wildlife refuge.
-
B.
hasWildlifeHabitats
Indicates that an entity contains or supports natural environments where wildlife species live, feed, or reproduce.
-
C.
hasWildlifeSite
chosen
Indicates that a location or entity possesses, contains, or is designated as a wildlife site.
-
D.
associatedWithWildlifeArea
Indicates that an entity has a connection, involvement, or linkage with a designated wildlife area.
-
E.
hasWildlifeObservationPoints
Indicates that a location or area includes designated points or spots where wildlife can be observed.
- 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_69e0b51cd5cc81909ac1187971e8a8ad |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69ee5baab4e081908916a289c607cf3a |
completed | April 26, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e6161feea4819091d13bb003363279 |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 5:01 p.m.