Triple
T34665008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CityCenter |
E890227
|
entity |
| Predicate | formerContains |
P79922
|
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, formerContains, Harmon Hotel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerContains Context triple: [CityCenter, formerContains, Harmon Hotel]
-
A.
alsoContains
Indicates that something includes, in addition to its primary contents, another specified element or component.
-
B.
believedToContain
Indicates that something is thought or assumed to hold, include, or possess something else, without certainty.
-
C.
currentContains
Indicates that one entity presently includes, encloses, or has another entity within its bounds or scope.
-
D.
typicallyContain
Indicates that one entity is normally or commonly found within, included in, or held by another entity under usual circumstances.
-
E.
previouslyContained
chosen
Indicates that one entity was contained within another entity at some point in the past, but is not necessarily contained there now.
- 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_6a0018cf6ebc8190aee6288788d0067e |
completed | May 10, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_6a001855e8588190a65840485473cf8b |
completed | May 10, 2026, 5:32 a.m. |
Created at: May 1, 2026, 2:04 a.m.