Triple
T25645338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decima battaglia dell'Isonzo |
E642943
|
entity |
| Predicate | conseguenza |
P812
|
FINISHED |
| Object | pesanti perdite per entrambi gli schieramenti |
—
|
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: pesanti perdite per entrambi gli schieramenti | Statement: [Decima battaglia dell'Isonzo, conseguenza, pesanti perdite per entrambi gli schieramenti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conseguenza Context triple: [Decima battaglia dell'Isonzo, conseguenza, pesanti perdite per entrambi gli schieramenti]
-
A.
consequenceInText
Indicates that one event, action, or state is presented in the text as a consequence or result of another.
-
B.
consequenceOfInfluence
Indicates that one event, state, or condition occurs as a result of the influence or impact exerted by another.
-
C.
hasConsequence
chosen
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
-
D.
consequenceOfApplication
Indicates that something occurs as a result or outcome of a particular application or use of something.
-
E.
avoidedConsequence
Indicates that an action or event prevented a particular consequence from occurring.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5faa437a481908d89a553f2406161 |
completed | May 2, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69f4a0f7c6008190ae8cee3e71e19b94 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 5:51 p.m.