Triple

T23765326
Position Surface form Disambiguated ID Type / Status
Subject Sveti Stefan E587360 entity
Predicate operatedBy P86 FINISHED
Object Aman Resorts
Aman Resorts is a luxury hotel and resort group known for its ultra-exclusive, architecturally distinctive properties and highly personalized service in destinations around the world.
E1600171 NE 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: Aman Resorts | Statement: [Sveti Stefan, operatedBy, Aman Resorts]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Aman Resorts
Triple: [Sveti Stefan, operatedBy, Aman Resorts]
Generated description
Aman Resorts is a luxury hotel and resort group known for its ultra-exclusive, architecturally distinctive properties and highly personalized service in destinations around the world.

Provenance (5 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_69e2490b8ac48190a6b35f1d5500486b completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1bdb5b0408190b46661d80e37b509 completed April 29, 2026, 8:13 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0f53de310081908831294237d2c388 completed May 21, 2026, 6:50 p.m.
NEDg Description generation batch_6a0f555a0a5c819089d26a13abebd43a completed May 21, 2026, 6:56 p.m.
NED2 Entity disambiguation (via description) batch_6a0f57ca769081908f3ae56eeb36bfba completed May 21, 2026, 7:06 p.m.
Created at: April 17, 2026, 7:15 p.m.