Triple
T30827526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Army Detachment Steiner |
E785115
|
entity |
| Predicate | locationOfPlannedAttack |
P81197
|
FINISHED |
| Object | north of Berlin |
—
|
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: north of Berlin | Statement: [Army Detachment Steiner, locationOfPlannedAttack, north of Berlin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfPlannedAttack Context triple: [Army Detachment Steiner, locationOfPlannedAttack, north of Berlin]
-
A.
plannedAttack
Indicates that an entity has intentionally prepared and organized an attack against a target.
-
B.
terroristAttackLocation
Indicates the place where a terrorist attack occurred or was carried out.
-
C.
bombingLocation
Indicates the place where a bombing event occurs or is carried out.
-
D.
hasPlannedAttackPoint
chosen
Indicates that an entity has designated or selected a specific location as the intended site for carrying out an attack.
-
E.
plannedAttackWith
Indicates that one entity has prepared or organized an attack using or involving another entity as the means or instrument of that attack.
- 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_69f224b6642481909e8d701de2cd1a53 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a01203ac018819085d7c9abd8345b23 |
completed | May 11, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_6a011f3f149c819090749722da0e3413 |
completed | May 11, 2026, 12:13 a.m. |
Created at: April 29, 2026, 8:44 p.m.