Triple
T10087823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | woodpecker finch |
E215264
|
entity |
| Predicate | exhibitsBehavior |
P23475
|
FINISHED |
| Object | tool use |
—
|
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: tool use | Statement: [woodpecker finch, exhibitsBehavior, tool use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exhibitsBehavior Context triple: [woodpecker finch, exhibitsBehavior, tool use]
-
A.
shapesBehaviorOf
Indicates that one entity influences, determines, or constrains the way another entity behaves or acts.
-
B.
definingBehavior
Indicates the characteristic action or pattern of actions that fundamentally determines or typifies how something functions or is understood.
-
C.
behaviorObserved
chosen
Indicates that a particular behavior or action has been witnessed, recorded, or detected in relation to an entity or context.
-
D.
behaviorCode
Indicates the specific rule, standard, or classification code that governs or characterizes an entity’s behavior in a given context.
-
E.
behaviorNear
Indicates that one entity exhibits a behavior or action in close spatial proximity to 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_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. |
Created at: March 30, 2026, 9:01 p.m.