Triple
T38240888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackwater Rush |
E1013755
|
entity |
| Predicate | usedInDefense |
P151595
|
FINISHED |
| Object | wildfire trap during the Battle of the Blackwater |
—
|
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: wildfire trap during the Battle of the Blackwater | Statement: [Blackwater Rush, usedInDefense, wildfire trap during the Battle of the Blackwater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInDefense Context triple: [Blackwater Rush, usedInDefense, wildfire trap during the Battle of the Blackwater]
-
A.
defensiveUse
Indicates that an entity uses something primarily for protection or defense against threats or attacks.
-
B.
usedInWar
Indicates that something (such as a resource, technology, or strategy) was employed as part of military activities or conflict in a war.
-
C.
defenseIncludes
Indicates that a defense strategy, plan, or system contains or incorporates a particular component, measure, or element as part of it.
-
D.
defenceUsed
chosen
Indicates that a particular defensive measure, tactic, or argument was employed in response to a threat, attack, or accusation.
-
E.
builtToDefendAgainst
Indicates that something was constructed or designed specifically for the purpose of protecting against or countering a particular threat, entity, or type of attack.
- 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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff3fb2318c81908a46c2f513608935 |
completed | May 9, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69ff3e96dcc48190819f6204680d84aa |
completed | May 9, 2026, 2:03 p.m. |
Created at: May 3, 2026, 4:30 p.m.