Triple
T25645334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decima battaglia dell'Isonzo |
E642943
|
entity |
| Predicate | esito |
P59870
|
FINISHED |
| Object | successo limitato per l'Italia |
—
|
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: successo limitato per l'Italia | Statement: [Decima battaglia dell'Isonzo, esito, successo limitato per l'Italia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: esito Context triple: [Decima battaglia dell'Isonzo, esito, successo limitato per l'Italia]
-
A.
result
Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
-
B.
outcomeOf
chosen
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
C.
initialOutcome
Indicates the result or state that first occurs at the beginning of a process, event, or interaction, before any subsequent changes or outcomes.
-
D.
supportedOutcomeOf
Indicates that one entity serves as evidence, backing, or justification for the outcome or result represented by another entity.
-
E.
outcomeOfTrial
Indicates that a particular result or verdict is produced as the consequence of a specific trial or legal proceeding.
- 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_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 5:51 p.m.