Triple
T18185649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cosey Hotel and Resort |
E435405
|
entity |
| Predicate | declinesInStatus |
P19208
|
FINISHED |
| Object | after Bill Cosey’s death |
—
|
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: after Bill Cosey’s death | Statement: [Cosey Hotel and Resort, declinesInStatus, after Bill Cosey’s death]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declinesInStatus Context triple: [Cosey Hotel and Resort, declinesInStatus, after Bill Cosey’s death]
-
A.
declineAfter
chosen
Indicates that one entity or value decreases or worsens following another specified event, condition, or point in time.
-
B.
declineIn
Indicates a relationship where one entity experiences a decrease or reduction in the level, amount, or intensity of another entity over time.
-
C.
declineOrEnd
Indicates that a relationship, process, or state is either decreasing in intensity or coming to a complete end.
-
D.
declineBeganInPeriod
Indicates that the onset of a decline in the subject occurred during the specified time period.
-
E.
decliningAs
Indicates that one entity is decreasing in value, intensity, or importance relative to another over time.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dffdccd881908da772db78b9d081 |
completed | April 19, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.