Triple
T23523131
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Homewood Suites by Hilton |
E574560
|
entity |
| Predicate | typicalStayPattern |
P153088
|
FINISHED |
| Object | longer-term stays |
—
|
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: longer-term stays | Statement: [Homewood Suites by Hilton, typicalStayPattern, longer-term stays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalStayPattern Context triple: [Homewood Suites by Hilton, typicalStayPattern, longer-term stays]
-
A.
typicalStopPattern
Indicates the usual or most common sequence or arrangement of stops associated with an entity’s operation or route.
-
B.
typicalGoing
Indicates that an entity is engaged in or undergoing a normal, expected instance of going or movement from one place to another.
-
C.
travelPattern
Indicates the typical routes, frequencies, and behaviors associated with how an entity moves or travels between locations.
-
D.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
E.
typicalPractice
Indicates that an action, behavior, or method is commonly or customarily done in a given context or by a given group.
- F. None of above. chosen
Provenance (4 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_69e245bb3dcc8190ba9a2b35972b58d0 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1ac70b7888190b4abc4f78bdf539c |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f12760784c8190aaeff002ef31febe |
completed | April 28, 2026, 9:32 p.m. |
Created at: April 17, 2026, 6:08 p.m.