Triple
T24122521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paranthropus aethiopicus |
E597700
|
entity |
| Predicate | notableSpecimenNickname |
P34841
|
FINISHED |
| Object | Black Skull |
—
|
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: Black Skull | Statement: [Paranthropus aethiopicus, notableSpecimenNickname, Black Skull]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSpecimenNickname Context triple: [Paranthropus aethiopicus, notableSpecimenNickname, Black Skull]
-
A.
hasNotableSpecimen
chosen
Indicates that an entity possesses or is associated with a specimen that is considered particularly significant, remarkable, or noteworthy.
-
B.
notableNickname
Indicates that one entity is a well-known or widely recognized nickname or moniker for another entity.
-
C.
commonNameOfNotableSpecies
Indicates that the subject is a commonly used vernacular or everyday name for a notable or well-known biological species.
-
D.
nicknamedFor
Indicates that one entity serves as the source, inspiration, or reason for another entity’s nickname.
-
E.
notableSpecies
Indicates that the subject is known for, or significantly associated with, the specified species.
- 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_69e288c74200819098ab875b592cb39f |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1dee5937c819092396751c23553ca |
completed | April 29, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:05 p.m.