Triple
T27271161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homo rudolfensis |
E688054
|
entity |
| Predicate | holotypeDiscoveryYear |
P162533
|
FINISHED |
| Object | 1972 |
—
|
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: 1972 | Statement: [Homo rudolfensis, holotypeDiscoveryYear, 1972]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holotypeDiscoveryYear Context triple: [Homo rudolfensis, holotypeDiscoveryYear, 1972]
-
A.
publicationDateOfFirstDescription
Indicates the date on which something was first formally described or documented in a publication.
-
B.
holotypeSpecimenNumber
Indicates the identifying specimen number assigned to the holotype that formally defines a taxon in biological classification.
-
C.
yearOfTaxonName
Indicates the specific year in which a particular taxon name was formally established or published.
-
D.
holotypeFoundOnPropertyOf
Indicates that the holotype specimen of a taxon was discovered on land owned or controlled by the referenced property holder.
-
E.
holotypeStatus
Indicates that an entity serves as the designated holotype specimen on which the formal description and name of a taxon are based.
- 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f62b9e5ba88190a3c0d46edec7afe7 |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f623a91b9c8190b2e2fdbc55cb89b6 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f625402d808190be8279d895d2b27f |
completed | May 2, 2026, 4:24 p.m. |
Created at: April 27, 2026, 10:59 a.m.