Triple
T24056829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paranthropus boisei |
E595828
|
entity |
| Predicate | originalGenusName |
P33921
|
FINISHED |
| Object | Zinjanthropus |
—
|
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: Zinjanthropus | Statement: [Paranthropus boisei, originalGenusName, Zinjanthropus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalGenusName Context triple: [Paranthropus boisei, originalGenusName, Zinjanthropus]
-
A.
previousGenus
chosen
Indicates that one genus was previously used as the taxonomic genus for an organism before being reclassified to another genus.
-
B.
originalBinomialName
Indicates that one entity is the original scientific (binomial) name that was first formally assigned to the other entity (typically a species or taxon).
-
C.
commonNameOfGenus
Indicates that the object is a commonly used name referring to the genus specified by the subject.
-
D.
firstDescribedAsGenusBy
Indicates that one entity was the first to formally describe another entity as a genus in a taxonomic or scientific context.
-
E.
namedAfterTypeGenus
Indicates that an entity (such as a taxonomic group) is named after its type genus.
- 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_69e288c184b081909f1f1751fb8e299a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1da50d6108190a36bffaa475c8b93 |
completed | April 29, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:34 p.m.