Triple
T751048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weeping Angels |
E15447
|
entity |
| Predicate | attackMethod |
P4333
|
FINISHED |
| Object | Touching victims to displace them in time |
—
|
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: Touching victims to displace them in time | Statement: [Weeping Angels, attackMethod, Touching victims to displace them in time]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackMethod Context triple: [Weeping Angels, attackMethod, Touching victims to displace them in time]
-
A.
attackType
chosen
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
B.
attackToolExample
Indicates that a specific tool or method is used as an example of how an attack is or can be carried out.
-
C.
notableAttack
Indicates that an entity carried out, was involved in, or is strongly associated with a particularly significant or well-known attack.
-
D.
attacker
Indicates a relationship where one entity initiates a harmful or hostile action against another entity.
-
E.
attackDate
Indicates the calendar date on which an attack or assault event took place.
- 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a64adf2c81908e48090be35dd9d9 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a5004f708190a984ee221716e19c |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.