Triple
T27079400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homo naledi |
E685550
|
entity |
| Predicate | evidenceOfCarnivoreActivityOnBones |
P161827
|
FINISHED |
| Object | minimal |
—
|
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: minimal | Statement: [Homo naledi, evidenceOfCarnivoreActivityOnBones, minimal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evidenceOfCarnivoreActivityOnBones Context triple: [Homo naledi, evidenceOfCarnivoreActivityOnBones, minimal]
-
A.
interpretationOfBones
Indicates the act of analyzing and deriving meaning or conclusions from bones, such as for medical, archaeological, or forensic purposes.
-
B.
numberOfBonesRecovered
Indicates the count of bones that have been found and recovered in relation to a particular subject or event.
-
C.
isCarnivorous
Indicates that an entity feeds primarily or exclusively on other animals.
-
D.
carnivorousType
Indicates that one entity is a type or category of organism that feeds primarily on other animals (is carnivorous).
-
E.
hasFossilEvidence
Indicates that there exists fossil-based evidence supporting the existence, occurrence, or characteristics of the related entity or event.
- 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_69ef14843b1481909d828b3d5a44550a |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6231822ac8190887ebcb3b6d86d2b |
completed | May 2, 2026, 4:15 p.m. |
| PD | Predicate disambiguation | batch_69f61b40f02081909bd9c3ea73249163 |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fa35ac48190890102c348ed81a0 |
completed | May 2, 2026, 4 p.m. |
Created at: April 27, 2026, 8:33 a.m.