Triple
T13751899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grizzly Ridge |
E330372
|
entity |
| Predicate | primarySpeciesCommonName |
P77570
|
FINISHED |
| Object | grizzly bear |
—
|
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: grizzly bear | Statement: [Grizzly Ridge, primarySpeciesCommonName, grizzly bear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySpeciesCommonName Context triple: [Grizzly Ridge, primarySpeciesCommonName, grizzly bear]
-
A.
mainPreySpecies
Indicates the species that serves as the primary prey or main food source for a given predator.
-
B.
lessCommonSpecies
Indicates that one species is less common or less frequently observed than another species within a given context or environment.
-
C.
commonNameOfNotableSpecies
Indicates that the subject is a commonly used vernacular or everyday name for a notable or well-known biological species.
-
D.
includesSpeciesCommonName
chosen
Indicates that an entity contains or specifies the common (vernacular) name of a species.
-
E.
hostSpecies
Indicates the species that serves as the host for another organism, agent, or entity.
- 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_69d81c573f288190aa2403d484fa3d49 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0215cfa08190aaed8b089aff217b |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:09 p.m.