Triple
T10087816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | woodpecker finch |
E215264
|
entity |
| Predicate | usesToolFor |
P91992
|
FINISHED |
| Object | extracting insects from tree bark |
—
|
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: extracting insects from tree bark | Statement: [woodpecker finch, usesToolFor, extracting insects from tree bark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesToolFor Context triple: [woodpecker finch, usesToolFor, extracting insects from tree bark]
-
A.
usesToolType
Indicates that an entity performs an action or fulfills a role by employing a specific type or category of tool.
-
B.
usedByTool
Indicates that a particular tool is employed or operated by a specified agent or entity.
-
C.
isToolOf
Indicates that one entity functions as an instrument or means used by another entity to perform tasks or achieve goals.
-
D.
officialToolFor
Indicates that one entity is formally designated or authorized as the standard or primary tool to be used for another entity or purpose.
-
E.
isToolIn
Indicates that a tool is located within or contained inside a specified space, container, or context.
- 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_69ca83a1eed081908b2e9580f2ebeea7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd04875748190a81d1e9ad68dda96 |
completed | April 2, 2026, 2:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4b97870481908f7a89df10d58a9e |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 9:01 p.m.