Triple
T25324719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ursus americanus vancouveri |
E634978
|
entity |
| Predicate | firstDescribedAsSubspeciesOf |
P184349
|
FINISHED |
| Object | Ursus americanus |
—
|
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: Ursus americanus | Statement: [Ursus americanus vancouveri, firstDescribedAsSubspeciesOf, Ursus americanus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstDescribedAsSubspeciesOf Context triple: [Ursus americanus vancouveri, firstDescribedAsSubspeciesOf, Ursus americanus]
-
A.
subspeciesOf
Indicates that one taxonomic group is a subspecific rank within, and directly derived from, another species.
-
B.
firstDescribedAsGenusBy
Indicates that one entity was the first to formally describe another entity as a genus in a taxonomic or scientific context.
-
C.
subspeciesCommonName
Indicates the common (non-scientific) name used to refer to a particular subspecies.
-
D.
subspeciesAncestry
Indicates that one subspecies is ancestrally derived from, or traces its lineage back to, another subspecies.
-
E.
subordinateSpecies
Indicates that one species is hierarchically or functionally subordinate to another species within a defined biological or ecological context.
- 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.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 21, 2026, 1:29 p.m.