Triple
T33724351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Via Rasella attack |
E864101
|
entity |
| Predicate | retaliationLocation |
P30305
|
FINISHED |
| Object | Fosse Ardeatine |
—
|
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: Fosse Ardeatine | Statement: [Via Rasella attack, retaliationLocation, Fosse Ardeatine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retaliationLocation Context triple: [Via Rasella attack, retaliationLocation, Fosse Ardeatine]
-
A.
reportedLocation
Indicates that an entity has been specified or recorded as being at a particular location, typically based on a report or observation rather than direct verification.
-
B.
punishmentLocation
chosen
Indicates the place or setting where a punishment is carried out or imposed.
-
C.
allegedSupportLocation
Indicates a claimed or reported place where support (such as assistance, resources, or backing) is said to have been provided or received.
-
D.
apseLocation
Indicates the specific place or position where an apse is situated within a larger structure or context.
-
E.
opposingLocation
Indicates that two entities are located directly opposite each other, typically across a defined reference such as a street, corridor, or boundary.
- 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:44 a.m.