Triple
T25645314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decima battaglia dell'Isonzo |
E642943
|
entity |
| Predicate | conflitto |
P1406
|
FINISHED |
| Object | Prima guerra mondiale |
—
|
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: Prima guerra mondiale | Statement: [Decima battaglia dell'Isonzo, conflitto, Prima guerra mondiale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conflitto Context triple: [Decima battaglia dell'Isonzo, conflitto, Prima guerra mondiale]
-
A.
conflictIn
chosen
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
B.
conflictBelligerent
Indicates that an entity is a participating belligerent (e.g., a country, group, or force) in a specific conflict.
-
C.
ongoingConflict
Indicates a sustained, unresolved state of opposition or hostilities continuing between the involved entities.
-
D.
conflictCountry
Indicates that there is an armed conflict or war involving the referenced country as a participant.
-
E.
relateradKonflikt
Indicates that there is a related or associated conflict between the entities involved.
- 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.