Triple
T23879132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gran Sasso raid |
E600149
|
entity |
| Predicate | ItalianGuardResistance |
P149692
|
FINISHED |
| Object | almost none |
—
|
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: almost none | Statement: [Gran Sasso raid, ItalianGuardResistance, almost none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ItalianGuardResistance Context triple: [Gran Sasso raid, ItalianGuardResistance, almost none]
-
A.
resistanceOrganization
Indicates an organization that actively opposes, resists, or fights against a dominant power, regime, or occupying force.
-
B.
ItalianLosses
chosen
Indicates that the relationship concerns losses (such as casualties, equipment, or territory) incurred by Italian forces or entities.
-
C.
italyParticipation
Indicates that an entity is involved in, takes part in, or is a participant in Italy-related events, activities, or contexts.
-
D.
alignedItalyWith
Indicates that one entity brought Italy into political, military, or ideological agreement or cooperation with another entity.
-
E.
ItalianForcesComposition
Indicates the makeup and structure of the Italian military forces involved in a particular context or operation.
- 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_69e295318e148190b9979d8fc02e168f |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cc03fdcc8190ad77155ae7e6eda5 |
completed | April 29, 2026, 9:14 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:23 p.m.