Triple
T25908158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Undicesima battaglia dell'Isonzo |
E652812
|
entity |
| Predicate | armaPrevalente |
P7745
|
FINISHED |
| Object | fanteria |
—
|
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: fanteria | Statement: [Undicesima battaglia dell'Isonzo, armaPrevalente, fanteria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armaPrevalente Context triple: [Undicesima battaglia dell'Isonzo, armaPrevalente, fanteria]
-
A.
typicalWeapon
chosen
Indicates that the object is a weapon commonly or characteristically used by the subject.
-
B.
armedBy
Indicates that one entity is supplied with weapons, equipment, or armaments by another entity.
-
C.
armedVariants
Indicates that one entity is a version or model of another that is equipped with weapons or enhanced armaments.
-
D.
lightArmament
Indicates that an entity is equipped with or characterized by relatively minimal or lightweight weaponry compared to standard or heavy armament.
-
E.
combatArm
Indicates that one entity serves as a primary fighting or operational warfare branch or component of another entity (such as an organization or military force).
- 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_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 22, 2026, 8:27 a.m.