Triple
T36143760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bombing of Himmel Street |
E1045386
|
entity |
| Predicate | occursInFictionalLocation |
P21117
|
FINISHED |
| Object | Himmel Street |
—
|
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: Himmel Street | Statement: [bombing of Himmel Street, occursInFictionalLocation, Himmel Street]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursInFictionalLocation Context triple: [bombing of Himmel Street, occursInFictionalLocation, Himmel Street]
-
A.
hasFictionalLocation
chosen
Indicates that an entity is associated with, set in, or takes place within a location that exists only in fiction rather than in the real world.
-
B.
hasBranchInFictionalLocation
Indicates that an organization maintains a branch, office, or presence within a fictional or imaginary location.
-
C.
basedInFictionalLocation
Indicates that an entity’s primary setting, origin, or operations occur in a fictional (non-real) location.
-
D.
residesInFictionalLocation
Indicates that an entity lives or is based in a location that is explicitly fictional or imaginary.
-
E.
locatedInFictionalEvent
Indicates that one entity (typically a place, object, or character) exists or occurs within the context or setting of a fictional event.
- 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_69f76e37ace88190a906b107d388f5d1 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7ba6d06f48190a71b5a2f19e2232f |
completed | May 3, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a4aad48190a62e41c5e39339d9 |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:08 p.m.