Triple
T27314136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sahelanthropus |
E689292
|
entity |
| Predicate | holotypeMaterial |
P121419
|
FINISHED |
| Object | cranium |
—
|
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: cranium | Statement: [Sahelanthropus, holotypeMaterial, cranium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holotypeMaterial Context triple: [Sahelanthropus, holotypeMaterial, cranium]
-
A.
holotypeStatus
Indicates that an entity serves as the designated holotype specimen on which the formal description and name of a taxon are based.
-
B.
holotypePreserves
chosen
Indicates that a designated holotype specimen physically preserves or contains the referenced biological material or features.
-
C.
holotypeSite
Indicates the location or site where the holotype specimen of a taxon was originally collected or designated.
-
D.
holotypeSpecimenNumber
Indicates the identifying specimen number assigned to the holotype that formally defines a taxon in biological classification.
-
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_69ef355c53a08190a8a92e355a7ce115 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 11:29 a.m.