Triple
T25245555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battaglia della Nona Isonzo |
E632591
|
entity |
| Predicate | defensiveSide |
P162574
|
FINISHED |
| Object | esercito austro-ungarico |
—
|
NE NERFINISHED |
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: esercito austro-ungarico | Statement: [Battaglia della Nona Isonzo, defensiveSide, esercito austro-ungarico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defensiveSide Context triple: [Battaglia della Nona Isonzo, defensiveSide, esercito austro-ungarico]
-
A.
defensiveRole
Indicates that an entity serves a protective or guarding function in relation to another entity or context.
-
B.
defensiveSuccess
Indicates that a defensive action successfully prevented or mitigated an opposing threat, attack, or adverse outcome.
-
C.
offensiveSide
Indicates which participant or entity is acting in an attacking or aggressive role within a conflict, competition, or confrontation.
-
D.
usedDefensiveLine
Indicates that an entity employed or deployed a particular defensive line as part of its strategy or actions.
-
E.
primaryDefensiveLine
Indicates the main line of defense that first engages or protects against an opposing force or threat.
- F. None of above. chosen
Provenance (4 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_69e75a8fdd3881909ba0b05aa5da92a7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f62b9e5ba88190a3c0d46edec7afe7 |
completed | May 2, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
| PDg | Predicate description generation | batch_69f627ad6d4c81909796d39d78e414f9 |
completed | May 2, 2026, 4:34 p.m. |
Created at: April 21, 2026, 1:10 p.m.