Triple
T25061247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King David Hotel, Jerusalem |
E627663
|
entity |
| Predicate | bombingTarget |
P136651
|
FINISHED |
| Object | British administrative headquarters |
—
|
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: British administrative headquarters | Statement: [King David Hotel, Jerusalem, bombingTarget, British administrative headquarters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bombingTarget Context triple: [King David Hotel, Jerusalem, bombingTarget, British administrative headquarters]
-
A.
bombingObjective
chosen
Indicates that one entity is the intended target or goal of a bombing action carried out by another entity.
-
B.
bombingLocation
Indicates the place where a bombing event occurs or is carried out.
-
C.
bombardmentMilitaryTargets
Indicates the action of directing explosive or artillery attacks specifically against military objectives or installations.
-
D.
bombingName
Indicates that an entity is the name or designated title of a specific bombing event or bombing attack.
-
E.
bombingPlatform
Indicates that one entity serves as the platform or means from which another entity conducts or carries out a bombing.
- 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_69e2ff2c45f48190afa28369f1df6786 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f4599935f0819088f542f6b702f6d5 |
completed | May 1, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:10 a.m.