Triple
T20211505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acromantulas |
E493495
|
entity |
| Predicate | knownToAttack |
P100267
|
FINISHED |
| Object | Humans |
—
|
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: Humans | Statement: [Acromantulas, knownToAttack, Humans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownToAttack Context triple: [Acromantulas, knownToAttack, Humans]
-
A.
notableAttack
Indicates that an entity carried out, was involved in, or is strongly associated with a particularly significant or well-known attack.
-
B.
oftenAttackedBy
Indicates that an entity is frequently the target of attacks carried out by another entity.
-
C.
collisionAttackKnown
Indicates that a collision-based attack method or vulnerability is known or has been discovered.
-
D.
attacksIf
Indicates that one entity initiates or carries out an attack on another entity when certain conditions are met.
-
E.
hasAttack
chosen
Indicates that one entity performs, possesses, or is associated with an attack directed toward 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ed5691c8190bf253b1d4ee6e88f |
completed | April 20, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:38 p.m.