Triple
T25645341
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decima battaglia dell'Isonzo |
E642943
|
entity |
| Predicate | fronteSecondario |
P112742
|
FINISHED |
| Object | settore di Gorizia |
—
|
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: settore di Gorizia | Statement: [Decima battaglia dell'Isonzo, fronteSecondario, settore di Gorizia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fronteSecondario Context triple: [Decima battaglia dell'Isonzo, fronteSecondario, settore di Gorizia]
-
A.
frontSector
Indicates that one entity is located in the forward-facing sector or region relative to another entity.
-
B.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
C.
side2
Indicates that an entity is positioned on, associated with, or corresponds to the second side of another entity or structure.
-
D.
secondarySurface
Indicates a relationship where one surface functions as a secondary or subordinate surface in relation to a primary or main surface.
-
E.
secondaryLine
chosen
Indicates that something serves as a secondary or auxiliary line in relation to a primary or main line.
- 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_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 5:51 p.m.