Triple
T26708170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | butcher birds |
E673335
|
entity |
| Predicate | toolUseLikeBehavior |
P49194
|
FINISHED |
| Object | use of thorns as functional tools for food processing |
—
|
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: use of thorns as functional tools for food processing | Statement: [butcher birds, toolUseLikeBehavior, use of thorns as functional tools for food processing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toolUseLikeBehavior Context triple: [butcher birds, toolUseLikeBehavior, use of thorns as functional tools for food processing]
-
A.
toolUse
chosen
Indicates that an entity uses or employs another entity as a tool to perform an action or achieve a goal.
-
B.
toolUseExamples
Indicates that one entity provides example instances or demonstrations of how a particular tool is or can be used by another entity.
-
C.
toolIn
Indicates that one entity is a tool or instrument used in or associated with another entity or context.
-
D.
toolMentioned
Indicates that a particular tool is referenced or brought up in the given context or interaction.
-
E.
toolDescribed
Indicates that one entity provides a description or explanation of a tool associated with another entity.
- 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_69eecda3a22881908f3061c760b9d542 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f617bb5a38819099dace3392694896 |
completed | May 2, 2026, 3:26 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:34 a.m.