Triple
T31769361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greenbrook Sanctuary |
E810894
|
entity |
| Predicate | managesHumanImpact |
P184394
|
FINISHED |
| Object | limited visitor capacity |
—
|
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: limited visitor capacity | Statement: [Greenbrook Sanctuary, managesHumanImpact, limited visitor capacity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesHumanImpact Context triple: [Greenbrook Sanctuary, managesHumanImpact, limited visitor capacity]
-
A.
humanImpact
Indicates the effect or influence that human activities have on another entity, system, or environment.
-
B.
examinesHumanImpactOnNature
Indicates examining how human activities affect or alter natural environments and ecosystems.
-
C.
humanImpactLevel
Indicates the degree or extent to which human activities affect or influence a given entity, system, or environment.
-
D.
conservationImpact
Indicates the effect that an action, policy, or entity has on the preservation, protection, or restoration of natural ecosystems and biodiversity.
-
E.
impactOnHumans
Indicates a relationship where something produces an effect, influence, or consequence on humans.
- F. None of above. chosen
Provenance (4 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69f7b0e3917481908a394680d76743c3 |
completed | May 3, 2026, 8:32 p.m. |
Created at: April 30, 2026, 11:33 p.m.