Triple
T8709053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stuart Ullman |
E206725
|
entity |
| Predicate | hasRelationshipToOverlookHotel |
P84664
|
FINISHED |
| Object | administrator |
—
|
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: administrator | Statement: [Stuart Ullman, hasRelationshipToOverlookHotel, administrator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRelationshipToOverlookHotel Context triple: [Stuart Ullman, hasRelationshipToOverlookHotel, administrator]
-
A.
hasResortHotel
Indicates that one entity owns, includes, or is associated with a resort hotel as part of its facilities or offerings.
-
B.
hasPartnerHotel
Indicates that one hotel has an established partnership or affiliation relationship with another hotel.
-
C.
isResortOf
Indicates that a location or facility functions as a resort associated with, belonging to, or serving a particular entity (such as a city, region, or organization).
-
D.
hasAccommodation
Indicates that an entity provides, owns, or is associated with a place for someone to stay or live.
-
E.
hasSisterResort
Indicates that one resort is formally associated with another as its sister property, typically under common ownership or branding.
- 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_69ca835645e881908f00e3c8b51da81d |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5c2e9c688190aceefaa2c3b7d7bd |
completed | March 31, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc582412f48190ae819965bfb0e75d |
completed | March 31, 2026, 11:26 p.m. |
Created at: March 30, 2026, 6:35 p.m.