Triple
T25966174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | former Grand Hotel Esplanade |
E645674
|
entity |
| Predicate | conditionAfterEvent |
P158418
|
FINISHED |
| Object | heavily 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: heavily damaged | Statement: [former Grand Hotel Esplanade, conditionAfterEvent, heavily damaged]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conditionAfterEvent Context triple: [former Grand Hotel Esplanade, conditionAfterEvent, heavily damaged]
-
A.
conditionAfterClosure
Indicates the state or circumstances that exist after a process, event, or entity has been formally closed or concluded.
-
B.
usedAfterEventFor
Indicates that one entity is used only after a specified event has occurred or been completed.
-
C.
triggerCondition
Indicates the specific circumstances or state under which an associated event, action, or process is initiated or activated.
-
D.
settingAfterEvent
chosen
Indicates that a particular setting or state occurs subsequent to, and as a result of or in temporal sequence with, a specified event.
-
E.
conditionalEffect
Indicates that one event, state, or action occurs or holds only if a specified condition is met.
- 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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f604c9e74c819090333e44f00abd17 |
completed | May 2, 2026, 2:06 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 8:48 a.m.