Triple
T27347987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homo habilis |
E684279
|
entity |
| Predicate | toolFunction |
P162207
|
FINISHED |
| Object | used tools for cutting and processing food |
—
|
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: used tools for cutting and processing food | Statement: [Homo habilis, toolFunction, used tools for cutting and processing food]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toolFunction Context triple: [Homo habilis, toolFunction, used tools for cutting and processing food]
-
A.
toolDeveloperFor
Indicates that one entity is the creator or developer of a tool that is used by or associated with another entity.
-
B.
toolIn
Indicates that one entity is a tool or instrument used in or associated with another entity or context.
-
C.
toolUse
Indicates that an entity uses or employs another entity as a tool to perform an action or achieve a goal.
-
D.
toolType
Indicates the specific kind or category of tool associated with an entity.
-
E.
toolDescribed
Indicates that one entity provides a description or explanation of a tool associated with another entity.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62ba48564819091f2f7f2db3178ce |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f620e4b1c88190a17940251abc68fd |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 27, 2026, 11:46 a.m.