Triple
T20070065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TAAF |
E499708
|
entity |
| Predicate | containsProtectedAreas |
P855
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [TAAF, containsProtectedAreas, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsProtectedAreas Context triple: [TAAF, containsProtectedAreas, true]
-
A.
hasProtectedAreasNearby
Indicates that an entity is located close to one or more designated protected or conservation areas.
-
B.
hasProtectedArea
chosen
Indicates that an entity possesses, includes, or is associated with a designated protected area for conservation or restricted use.
-
C.
hasProtectedAreaStatus
Indicates that an area is officially designated and managed as a protected area under relevant conservation or legal frameworks.
-
D.
hasNeighbouringProtectedArea
Indicates that one protected area is directly adjacent to or shares a boundary with another protected area.
-
E.
hasProtectedAreaAuthority
Indicates that an entity holds official authority or responsibility for managing or overseeing a 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6643798a4819081fa4e71c74b47bc |
completed | April 20, 2026, 5:36 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:39 p.m.