Triple
T28136448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rank Hotels |
E714218
|
entity |
| Predicate | dissolvedOrEnded |
P138719
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Rank Hotels, dissolvedOrEnded, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dissolvedOrEnded Context triple: [Rank Hotels, dissolvedOrEnded, 20th century]
-
A.
hasDissolutionDate
Indicates the date on which an entity, such as an organization or legal arrangement, formally ceases to exist or is officially dissolved.
-
B.
dissolvedWhen
chosen
Indicates that one entity ceases to exist, function, or remain intact at the time or under the conditions specified by another entity or event.
-
C.
wasDissolvedAfter
Indicates that one entity ceased to exist or operate at a later point in time than another entity’s dissolution.
-
D.
dissolvedBefore
Indicates that one entity ceased to exist, function, or remain in solution at an earlier time than another entity.
-
E.
endedByDissolution
Indicates that a relationship, agreement, or entity was terminated specifically through a formal dissolution process.
- 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_69efd6af156c81908f50c2cd7db0e1ef |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f641309d94819090cdbc66bbcb32e1 |
completed | May 2, 2026, 6:23 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 9:50 p.m.