Triple
T25101774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ursus americanus californiensis |
E628745
|
entity |
| Predicate | describedAsSubspeciesOf |
P28088
|
FINISHED |
| Object | American black bear |
—
|
NE NERFINISHED |
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: American black bear | Statement: [Ursus americanus californiensis, describedAsSubspeciesOf, American black bear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: describedAsSubspeciesOf Context triple: [Ursus americanus californiensis, describedAsSubspeciesOf, American black bear]
-
A.
subspeciesOf
chosen
Indicates that one taxonomic group is a subspecific rank within, and directly derived from, another species.
-
B.
subspeciesCommonName
Indicates the common (non-scientific) name used to refer to a particular subspecies.
-
C.
subspeciesIncludes
Indicates that a particular subspecies contains or encompasses the referenced member entities within its taxonomic grouping.
-
D.
hasEndemicSubspecies
Indicates that a species has one or more subspecies that are native and restricted to a particular geographic area.
-
E.
recognizedSubspeciesCount
Indicates the number of subspecies that are formally recognized for a given species or taxon.
- 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_69e2ff3071548190b62d1ac237397197 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f464bd4d7081909fc0db6b8bf897b9 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:25 a.m.