Triple
T6467161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2004 Madrid train bombings |
E142258
|
entity |
| Predicate | transportModeAttacked |
P21178
|
FINISHED |
| Object | train |
—
|
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: train | Statement: [2004 Madrid train bombings, transportModeAttacked, train]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportModeAttacked Context triple: [2004 Madrid train bombings, transportModeAttacked, train]
-
A.
transportAttacked
chosen
Indicates that a transport vehicle or conveyance was subjected to an attack or hostile action.
-
B.
attackedFrom
Indicates that one entity initiated an attack against another entity originating from a specific source location or position.
-
C.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
D.
attackedIn
Indicates that one entity carried out an attack in the location, context, or time frame specified by another entity or value.
-
E.
transportThreat
Indicates a relationship where an entity moves or conveys a threat from one place or context to another.
- 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_69c008d3bf4c8190bcf798c5ba9d6fb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06a12ccf481908f71f888cd744b64 |
completed | March 22, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69c0673d46a08190bc8bcd29f9555fe7 |
completed | March 22, 2026, 10:03 p.m. |
Created at: March 22, 2026, 4:49 p.m.