Triple
T32397398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oktyabrskaya Hotel |
E827847
|
entity |
| Predicate | checkInAvailable |
P12450
|
FINISHED |
| Object | 24-hour |
—
|
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: 24-hour | Statement: [Oktyabrskaya Hotel, checkInAvailable, 24-hour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: checkInAvailable Context triple: [Oktyabrskaya Hotel, checkInAvailable, 24-hour]
-
A.
hasCheckInSystem
Indicates that an entity uses or is equipped with a system for registering or recording check-ins.
-
B.
checkInTime
chosen
Indicates the time at which an entity arrives at and formally registers its presence at a specified place or event.
-
C.
initialAvailability
Indicates the starting level or state of availability of an entity before any changes or updates occur.
-
D.
packageAvailability
Indicates whether a particular package is currently available for use, access, or distribution.
-
E.
kitAvailability
Indicates that a particular kit is available for use, access, or distribution in a given context.
- 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c216aa9c819095e8268116230dd0 |
completed | May 3, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:52 a.m.