Triple
T25245556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battaglia della Nona Isonzo |
E632591
|
entity |
| Predicate | offensiveSide |
P158314
|
FINISHED |
| Object | esercito italiano |
—
|
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: esercito italiano | Statement: [Battaglia della Nona Isonzo, offensiveSide, esercito italiano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offensiveSide Context triple: [Battaglia della Nona Isonzo, offensiveSide, esercito italiano]
-
A.
offenseTeam
Indicates which team is currently playing offense in a game or sporting context.
-
B.
offensiveStrength
Indicates the degree or capacity of an entity to carry out effective attacks or aggressive actions against an opponent.
-
C.
offensiveStrategy
Indicates a strategic approach focused on attacking or aggressively advancing against an opponent.
-
D.
offensiveForce
Indicates the use or application of aggressive or attacking power or violence by one entity against another.
-
E.
offensiveTackle
Indicates that an entity plays the offensive tackle position, responsible for blocking and protecting on the offensive line in a gridiron football context.
- F. None of above. chosen
Provenance (4 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_69e75a8fdd3881909ba0b05aa5da92a7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4808619248190a9eb6848a2a81d55 |
completed | May 1, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f465699c9c8190ac7b4b32b782550c |
completed | May 1, 2026, 8:33 a.m. |
Created at: April 21, 2026, 1:10 p.m.