Triple
T12693137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ellerman Investments |
E303257
|
entity |
| Predicate | hotelCategoryOfOwnedAsset |
P16578
|
FINISHED |
| Object | five-star hotel |
—
|
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: five-star hotel | Statement: [Ellerman Investments, hotelCategoryOfOwnedAsset, five-star hotel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hotelCategoryOfOwnedAsset Context triple: [Ellerman Investments, hotelCategoryOfOwnedAsset, five-star hotel]
-
A.
hotelCategory
Indicates the classification or rating level assigned to a hotel (e.g., star rating or category tier).
-
B.
hotelClass
chosen
Indicates the classification or rating level assigned to a hotel, such as its star category or quality tier.
-
C.
hasHotelType
Indicates that a hotel is classified as belonging to a specific type or category (e.g., resort, boutique, hostel).
-
D.
locatedInHotelCategory
Indicates that one entity is situated within, or belongs to, a specific category or classification of hotels.
-
E.
reservationCategory
Indicates the classification or type assigned to a reservation (such as its purpose, priority, or usage group) within a system.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d962a32c6481908ddaddae4ea267bf |
completed | April 10, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69d960be63f081908a5ef5ef17a311bf |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:22 p.m.