Triple
T28766783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nguru Mountains |
E726292
|
entity |
| Predicate | protectedAreaPresence |
P855
|
FINISHED |
| Object | forest reserves |
—
|
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: forest reserves | Statement: [Nguru Mountains, protectedAreaPresence, forest reserves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectedAreaPresence Context triple: [Nguru Mountains, protectedAreaPresence, forest reserves]
-
A.
protectedAreaGateway
Indicates that an entity serves as an entrance or access point leading into a protected or restricted area.
-
B.
protectsArea
Indicates that one entity serves to guard, defend, or preserve a particular area or region from harm or intrusion.
-
C.
hasProtectedAreaAccess
Indicates that an entity is permitted to enter, use, or otherwise access a designated protected area under defined conditions.
-
D.
hasProtectedArea
chosen
Indicates that an entity possesses, includes, or is associated with a designated protected area for conservation or restricted use.
-
E.
protectedAreaAssociation
Indicates an association where one entity is designated as, or linked to, a protected area in relation to another entity.
- 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_69f03198be14819098fa74e48b3749bf |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 6:14 a.m.