Triple
T18523772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valeriano Abanador |
E452659
|
entity |
| Predicate | usedDisguise |
P22080
|
FINISHED |
| Object | civilian appearance of attackers |
—
|
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: civilian appearance of attackers | Statement: [Valeriano Abanador, usedDisguise, civilian appearance of attackers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedDisguise Context triple: [Valeriano Abanador, usedDisguise, civilian appearance of attackers]
-
A.
disguisedAs
Indicates that one entity is intentionally presenting itself as, or made to appear as, another entity in order to conceal its true identity.
-
B.
reasonForDisguise
Indicates the motive or purpose behind an entity adopting a disguise.
-
C.
usesMasksOrDisguises
chosen
Indicates that an entity employs masks, costumes, or other forms of disguise to conceal or alter its identity in the context of an action or interaction.
-
D.
usedCover
Indicates that one entity employed another entity as a protective or concealing cover in a given context.
-
E.
usedPseudonym
Indicates that an entity performed an action or participated in a context under a name that was not their real or primary identity.
- 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e533908b0c81908725baf828aa46ff |
completed | April 19, 2026, 7:57 p.m. |
| PD | Predicate disambiguation | batch_69e469e0025c81908f16ed4f922674af |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.