Triple
T37939465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sooretama |
E946443
|
entity |
| Predicate | hasProtectedAreaTypeNearby |
P96189
|
FINISHED |
| Object | biological reserve |
—
|
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: biological reserve | Statement: [Sooretama, hasProtectedAreaTypeNearby, biological reserve]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtectedAreaTypeNearby Context triple: [Sooretama, hasProtectedAreaTypeNearby, biological reserve]
-
A.
hasProtectedAreasNearby
chosen
Indicates that an entity is located close to one or more designated protected or conservation areas.
-
B.
hasNeighbouringProtectedArea
Indicates that one protected area is directly adjacent to or shares a boundary with another protected area.
-
C.
isInProtectedAreaVicinity
Indicates that an entity is located close to, but not necessarily within, a designated protected area.
-
D.
hasProtectedArea
Indicates that an entity possesses, includes, or is associated with a designated protected area for conservation or restricted use.
-
E.
isProtectedAreaOf
Indicates that a designated protected area (such as a park or reserve) is established to conserve and manage a specific geographic region or natural feature.
- 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_69f76ef531ac8190ae6d99e5786e76ec |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.