Triple
T19527938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saumur railway tunnel |
E488579
|
entity |
| Predicate | attackOutcome |
P100772
|
FINISHED |
| Object | successfully damaged |
—
|
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: successfully damaged | Statement: [Saumur railway tunnel, attackOutcome, successfully damaged]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackOutcome Context triple: [Saumur railway tunnel, attackOutcome, successfully damaged]
-
A.
attackEffect
chosen
Indicates that one entity’s attack produces a specific effect or consequence on another entity.
-
B.
attackOccurred
Indicates that an act of aggression or violence was carried out by one party against another.
-
C.
impactOutcome
Indicates that one entity produces an effect or influence that changes the result, consequence, or final state of another entity or situation.
-
D.
statusAfterAttack
Indicates the resulting condition or state of an entity after an attack has occurred.
-
E.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6363d43148190af25caaa57accf9b |
completed | April 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.