Triple
T20349277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blast-Ended Skrewts |
E495964
|
entity |
| Predicate | behaviour |
P23475
|
FINISHED |
| Object | aggressive toward handlers |
—
|
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: aggressive toward handlers | Statement: [Blast-Ended Skrewts, behaviour, aggressive toward handlers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: behaviour Context triple: [Blast-Ended Skrewts, behaviour, aggressive toward handlers]
-
A.
behaviorNear
Indicates that one entity exhibits a behavior or action in close spatial proximity to another entity.
-
B.
behaviorObserved
chosen
Indicates that a particular behavior or action has been witnessed, recorded, or detected in relation to an entity or context.
-
C.
behaviorCode
Indicates the specific rule, standard, or classification code that governs or characterizes an entity’s behavior in a given context.
-
D.
definingBehavior
Indicates the characteristic action or pattern of actions that fundamentally determines or typifies how something functions or is understood.
-
E.
workBehavior
Indicates how an entity typically acts, performs, or conducts itself in a work or professional context.
- 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_69e0b4a3320881909495ae8bc30bc2dc |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6783af5dc8190a40c3b9816cd1aef |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:24 a.m.