Triple
T6846283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edinburgh Princes Street station |
E157901
|
entity |
| Predicate | hadStationHotel |
P73485
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Edinburgh Princes Street station, hadStationHotel, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadStationHotel Context triple: [Edinburgh Princes Street station, hadStationHotel, yes]
-
A.
hasHotelType
Indicates that a hotel is classified as belonging to a specific type or category (e.g., resort, boutique, hostel).
-
B.
hotelClass
Indicates the classification or rating level assigned to a hotel, such as its star category or quality tier.
-
C.
hotelBrand
Indicates that a hotel is affiliated with, operated by, or marketed under a specific hotel brand.
-
D.
hotelConnection
Indicates a relationship where one entity is linked or associated with a hotel, such as being located in, connected to, or serviced by that hotel.
-
E.
hotelCategory
Indicates the classification or rating level assigned to a hotel (e.g., star rating or category tier).
- 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_69c6882ed4c081909dc465a7cf8838be |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d7cbe4488190b41ddf953f12f55f |
completed | March 27, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69c6d09f90648190bc0a462c7d59de1b |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d623aba88190a93ec9c83508c960 |
completed | March 27, 2026, 7:10 p.m. |
Created at: March 27, 2026, 2:20 p.m.