Triple
T25908143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Undicesima battaglia dell'Isonzo |
E652812
|
entity |
| Predicate | seguitaDa |
P134
|
FINISHED |
| Object | Dodicesima battaglia dell'Isonzo |
—
|
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: Dodicesima battaglia dell'Isonzo | Statement: [Undicesima battaglia dell'Isonzo, seguitaDa, Dodicesima battaglia dell'Isonzo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seguitaDa Context triple: [Undicesima battaglia dell'Isonzo, seguitaDa, Dodicesima battaglia dell'Isonzo]
-
A.
يتبعها
Indicates that one entity comes after, succeeds, or is subordinate to another in order, sequence, or hierarchy.
-
B.
continuedBy
Indicates that one entity carries on, extends, or resumes the activity, process, or sequence initiated by another entity.
-
C.
follows
chosen
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
-
D.
followsSect
Indicates that one entity adheres to, practices, or is a member of a particular sect associated with another entity.
-
E.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
- 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_69e7ab3d3f8481909bc53ed64c06af33 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f603c15b348190a7f00745b6475b28 |
completed | May 2, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 8:27 a.m.