Triple
T5893150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottoman army caught while crossing the Tisa River |
E131037
|
entity |
| Predicate | hasCauseOfVulnerability |
P708
|
FINISHED |
| Object | army engaged in river crossing |
—
|
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: army engaged in river crossing | Statement: [Ottoman army caught while crossing the Tisa River, hasCauseOfVulnerability, army engaged in river crossing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCauseOfVulnerability Context triple: [Ottoman army caught while crossing the Tisa River, hasCauseOfVulnerability, army engaged in river crossing]
-
A.
vulnerabilityType
Indicates the specific kind or category of vulnerability associated with an entity or situation.
-
B.
hasCause
chosen
Indicates that one entity is the reason for, or brings about, the occurrence or existence of another entity or event.
-
C.
susceptibleTo
Indicates that one entity is vulnerable or likely to be affected, harmed, or influenced by another entity or factor.
-
D.
hasProposedCause
Indicates that one entity is suggested or hypothesized to be the cause or explanation for another entity or event.
-
E.
hasSecurityConsideration
Indicates that there is a relevant security-related issue, risk, or precaution associated with the referenced 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_69c00857439c819095950754176aa58a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0334dc8248190b7394dcece362d52 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:58 p.m.