Triple
T23523059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hampton by Hilton |
E574559
|
entity |
| Predicate | typicalPositioning |
P153087
|
FINISHED |
| Object | affordable accommodations |
—
|
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: affordable accommodations | Statement: [Hampton by Hilton, typicalPositioning, affordable accommodations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPositioning Context triple: [Hampton by Hilton, typicalPositioning, affordable accommodations]
-
A.
typicalPositionType
Indicates the usual or most common positional role or placement type that an entity generally occupies or is associated with.
-
B.
positioning
Indicates the spatial or contextual arrangement of one entity relative to another or within a given environment.
-
C.
typicalAlignment
Indicates the usual or most common way in which two entities are positioned, oriented, or arranged relative to each other.
-
D.
typicalRecipientPosition
Indicates the usual or expected spatial or organizational position where a recipient is located relative to the action or source.
-
E.
stylePositioning
Indicates how an entity is spatially or visually arranged or aligned relative to a reference frame or other elements.
- 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.