Triple
T29554128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rucervus eldii eldii |
E749857
|
entity |
| Predicate | hasSubspeciesOf |
P28088
|
FINISHED |
| Object | Rucervus eldii |
—
|
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: Rucervus eldii | Statement: [Rucervus eldii eldii, hasSubspeciesOf, Rucervus eldii]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubspeciesOf Context triple: [Rucervus eldii eldii, hasSubspeciesOf, Rucervus eldii]
-
A.
subspeciesOf
chosen
Indicates that one taxonomic group is a subspecific rank within, and directly derived from, another species.
-
B.
subspeciesIncludes
Indicates that a particular subspecies contains or encompasses the referenced member entities within its taxonomic grouping.
-
C.
hasSubtaxon
Indicates that one taxonomic group is a subordinate or included taxon within another taxonomic group.
-
D.
subordinateSpecies
Indicates that one species is hierarchically or functionally subordinate to another species within a defined biological or ecological context.
-
E.
belongsToSubfamily
Indicates that one entity is a member of, or classified within, a specific subfamily of another 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_69f0bd4919e48190942b2a13d5b97d03 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: April 28, 2026, 5:14 p.m.