Triple
T25645315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decima battaglia dell'Isonzo |
E642943
|
entity |
| Predicate | fronte |
P2502
|
FINISHED |
| Object | fronte italiano |
—
|
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: fronte italiano | Statement: [Decima battaglia dell'Isonzo, fronte, fronte italiano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fronte Context triple: [Decima battaglia dell'Isonzo, fronte, fronte italiano]
-
A.
front
Indicates that one entity is located directly before or facing another entity along a primary viewing or movement direction.
-
B.
frontLine
chosen
Indicates that an entity is positioned at or associated with the foremost or primary line of engagement, activity, or defense relative to others.
-
C.
frontIn
Indicates that one entity is positioned directly in front of another entity in space or sequence.
-
D.
frontType
Indicates the type or category of a front (e.g., boundary or leading side) that one entity presents or forms relative to another.
-
E.
frontLineBetween
Indicates that a boundary or line of direct confrontation exists separating two opposing sides or regions.
- 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.