Triple
T31571586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isandlwana village |
E805578
|
entity |
| Predicate | hasNearbyProtectedAreaType |
P198639
|
FINISHED |
| Object | heritage conservation area |
—
|
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: heritage conservation area | Statement: [Isandlwana village, hasNearbyProtectedAreaType, heritage conservation area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyProtectedAreaType Context triple: [Isandlwana village, hasNearbyProtectedAreaType, heritage conservation area]
-
A.
hasProtectedAreasNearby
Indicates that an entity is located close to one or more designated protected or conservation areas.
-
B.
isInProtectedAreaVicinity
Indicates that an entity is located close to, but not necessarily within, a designated protected area.
-
C.
hasNeighbouringProtectedArea
Indicates that one protected area is directly adjacent to or shares a boundary with another protected area.
-
D.
nearbyProtectedAreaType
chosen
Indicates that an entity is located near a protected area and specifies the type or category of that nearby protected area.
-
E.
isInProtectedArea
Indicates that an entity is located within a designated protected or conservation 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_69f348d2ee94819091918d1789398c29 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff0491409c8190be40f633a58da0b1 |
completed | May 9, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69ff040bb5cc81909534c7eee85d5e90 |
completed | May 9, 2026, 9:53 a.m. |
Created at: April 30, 2026, 10:20 p.m.