Triple
T24056832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paranthropus boisei |
E595828
|
entity |
| Predicate | currentAcceptedName |
P107135
|
FINISHED |
| Object | Paranthropus boisei |
—
|
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: Paranthropus boisei | Statement: [Paranthropus boisei, currentAcceptedName, Paranthropus boisei]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentAcceptedName Context triple: [Paranthropus boisei, currentAcceptedName, Paranthropus boisei]
-
A.
isAcceptedName
chosen
Indicates that a given name is the currently recognized, valid, and officially accepted designation for an entity within a particular naming or classification system.
-
B.
currentName
Indicates the present or most recently assigned name associated with an entity.
-
C.
nomenclaturalStatus
Indicates the formal taxonomic or naming status assigned to a scientific name (e.g., valid, invalid, synonym, provisional) within a nomenclatural system.
-
D.
eraNameUsedInDocuments
Indicates that a particular era name is used as a temporal reference in the specified documents.
-
E.
currentOfficialNameSince
Indicates the date or time from which an entity has borne its current official name.
- 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.