Triple
T25645320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decima battaglia dell'Isonzo |
E642943
|
entity |
| Predicate | paeseCoinvolto |
P1059
|
FINISHED |
| Object | Impero 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: Impero austro-ungarico | Statement: [Decima battaglia dell'Isonzo, paeseCoinvolto, Impero austro-ungarico]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paeseCoinvolto Context triple: [Decima battaglia dell'Isonzo, paeseCoinvolto, Impero austro-ungarico]
-
A.
involvedCountry
chosen
Indicates that a country participates in, is associated with, or is otherwise implicated in the referenced event, activity, or situation.
-
B.
país
Indicates that an entity is a country (a sovereign state or nation) in relation to something else.
-
C.
affectedCountry
Indicates that a particular country is impacted or influenced by an event, action, or condition.
-
D.
countryPortionIn
Indicates that a specific part or region is located within the boundaries of a particular country.
-
E.
continentInvolved
Indicates that a particular continent participates in, is affected by, or plays a role in a specified event, process, or relationship.
- 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_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 21, 2026, 5:51 p.m.