Triple
T20800542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bruce Trail Conservancy |
E512025
|
entity |
| Predicate | conservationAreaType |
P5067
|
FINISHED |
| Object | escarpment lands |
—
|
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: escarpment lands | Statement: [Bruce Trail Conservancy, conservationAreaType, escarpment lands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conservationAreaType Context triple: [Bruce Trail Conservancy, conservationAreaType, escarpment lands]
-
A.
stateProtectedAreaType
Indicates that an area is designated as a specific type or category of state-protected area.
-
B.
relatedProtectedAreaType
Indicates that one protected area is associated with another through a specific type of protected-area relationship or classification.
-
C.
partOfProtectedAreaCategory
chosen
Indicates that one protected area belongs to, or is classified under, a specific protected area category.
-
D.
isTypeOfProtectedArea
Indicates that one entity is classified as a specific type or category of protected area in relation to another entity.
-
E.
typeOfConservation
Indicates the specific kind or category of conservation practice, method, or approach that applies to an entity or situation.
- 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_69e0b4cc69f481908e98751e697b9df4 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2b014648190a1133836b36c26cd |
completed | April 21, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69e5c0575b1c81908d010223fcd1213e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:39 p.m.