Triple
T23847361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pennsylvania Navy |
E592060
|
entity |
| Predicate | usedDefensiveMeasures |
P151595
|
FINISHED |
| Object | river obstructions |
—
|
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: river obstructions | Statement: [Pennsylvania Navy, usedDefensiveMeasures, river obstructions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedDefensiveMeasures Context triple: [Pennsylvania Navy, usedDefensiveMeasures, river obstructions]
-
A.
defensiveUse
Indicates that an entity uses something primarily for protection or defense against threats or attacks.
-
B.
hasDefensivePurpose
Indicates that something exists or is designed with the primary goal of protection, defense, or safeguarding against threats or harm.
-
C.
defenceUsed
chosen
Indicates that a particular defensive measure, tactic, or argument was employed in response to a threat, attack, or accusation.
-
D.
defendsHerselfBy
Indicates that a female entity protects or justifies herself using a specified method, action, or means.
-
E.
usedDefensiveLine
Indicates that an entity employed or deployed a particular defensive line as part of its strategy or actions.
- 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_69e25d221d908190b9b502ad31e66a3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c88c9bbc81909204120279e6d980 |
completed | April 29, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f1614612b481908c45d99e588882f9 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:10 p.m.