Triple
T27271162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homo rudolfensis |
E688054
|
entity |
| Predicate | holotypeDiscoverer |
P412
|
FINISHED |
| Object | Bernard Ngeneo |
—
|
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: Bernard Ngeneo | Statement: [Homo rudolfensis, holotypeDiscoverer, Bernard Ngeneo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holotypeDiscoverer Context triple: [Homo rudolfensis, holotypeDiscoverer, Bernard Ngeneo]
-
A.
taxonomicAuthority
Indicates the entity that formally described, named, or classified another entity in a taxonomic context.
-
B.
holotypeDiscoveryYear
Indicates the calendar year in which the holotype specimen for a taxon was first discovered.
-
C.
discoveredBy
chosen
Indicates that something was found, identified, or brought to light through the efforts or actions of a particular agent.
-
D.
holotypeRepository
Indicates the institution or collection where the designated holotype specimen of a taxon is stored or curated.
-
E.
holotypeFoundOnPropertyOf
Indicates that the holotype specimen of a taxon was discovered on land owned or controlled by the referenced property holder.
- 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f62cd2ceb481908cd9fae52a542206 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 10:59 a.m.