Triple
T347980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taylor Creek Visitor Center |
E6981
|
entity |
| Predicate | typicalWildlifeViewed |
P965
|
FINISHED |
| Object | black bears |
—
|
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: black bears | Statement: [Taylor Creek Visitor Center, typicalWildlifeViewed, black bears]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWildlifeViewed Context triple: [Taylor Creek Visitor Center, typicalWildlifeViewed, black bears]
-
A.
notableSpecies
chosen
Indicates that the subject is known for, or significantly associated with, the specified species.
-
B.
fauna
Indicates that an entity is an animal or part of the animal life associated with a particular place or context.
-
C.
faunaCharacteristic
Indicates that an entity has a specific trait, feature, or quality related to animals or animal life.
-
D.
featuresSpecies
Indicates that something includes, presents, or highlights a particular species as part of its content or composition.
-
E.
hasEndemicSpecies
Indicates that a place or region contains species that are native to and found only within that specific geographic 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb1c1c908190b3a01de893207ed1 |
completed | Feb. 28, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69a2e95451a4819090f4e4fb9b21a493 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.