Triple
T32397392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oktyabrskaya Hotel |
E827847
|
entity |
| Predicate | servesBusinessTravelers |
P57247
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Oktyabrskaya Hotel, servesBusinessTravelers, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesBusinessTravelers Context triple: [Oktyabrskaya Hotel, servesBusinessTravelers, true]
-
A.
servesBusinessTravel
chosen
Indicates that an entity provides services or accommodations specifically intended for business-related travel.
-
B.
servesTravelersTo
Indicates a relationship where one entity provides services, assistance, or accommodations specifically directed toward travelers heading to a particular destination.
-
C.
servedTravelersBetween
Indicates that an entity provided transportation service for travelers moving between two specified locations.
-
D.
servesRidersTraveling
Indicates that a service or entity provides transportation-related service or support to riders who are currently traveling or in transit.
-
E.
servesFlightsTo
Indicates that one transportation provider regularly operates flights to a specified destination location.
- 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_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
Created at: May 1, 2026, 12:52 a.m.