Triple
T25645328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decima battaglia dell'Isonzo |
E642943
|
entity |
| Predicate | precedutaDa |
P25144
|
FINISHED |
| Object | Nona 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: Nona battaglia dell'Isonzo | Statement: [Decima battaglia dell'Isonzo, precedutaDa, Nona battaglia dell'Isonzo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedutaDa Context triple: [Decima battaglia dell'Isonzo, precedutaDa, Nona battaglia dell'Isonzo]
-
A.
precedesDisc
Indicates that one discourse segment or unit occurs before another in the sequence of discourse.
-
B.
cededTo
Indicates that control, ownership, or authority over something was formally transferred from one entity to another.
-
C.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
D.
wasPrecededBy
chosen
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
E.
precedentFor
Indicates that one situation, decision, or case serves as an authoritative example or basis for deciding or interpreting another.
- 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_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 21, 2026, 5:51 p.m.