Triple
T34665009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CityCenter |
E890227
|
entity |
| Predicate | demolitionOfComponent |
P167973
|
FINISHED |
| Object | Harmon Hotel |
—
|
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: Harmon Hotel | Statement: [CityCenter, demolitionOfComponent, Harmon Hotel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demolitionOfComponent Context triple: [CityCenter, demolitionOfComponent, Harmon Hotel]
-
A.
destroyedPart
chosen
Indicates that one entity has caused damage to or ruined a portion or component of another entity.
-
B.
demolitionEnd
Indicates the point in time or event at which a demolition process is completed or comes to an end.
-
C.
demolitionContext
Indicates that an entity is involved in or associated with the circumstances, setting, or conditions under which a demolition activity occurs.
-
D.
demolitionMethod
Indicates the technique or process used to carry out a demolition.
-
E.
demolished
Indicates that one entity completely destroyed or razed another entity, typically a structure or object, so that it no longer exists in its previous form.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f722f574388190b75d8c00917bb6f5 |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:04 a.m.