Triple
T28031128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ormond Hotel |
E708268
|
entity |
| Predicate | targetedClientele |
P163231
|
FINISHED |
| Object | wealthy tourists |
—
|
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: wealthy tourists | Statement: [Ormond Hotel, targetedClientele, wealthy tourists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetedClientele Context triple: [Ormond Hotel, targetedClientele, wealthy tourists]
-
A.
targetMarket
Indicates the group of consumers or organizations that a product, service, or campaign is specifically intended and designed to reach.
-
B.
targetQualification
Indicates that one entity specifies or defines the required qualification or eligibility criteria for another entity.
-
C.
targetedPopulation
Indicates the group of individuals or entities that an action, intervention, or effect is specifically directed toward.
-
D.
targetOutcomeForClients
Indicates the specific result or benefit that an action, service, or process is intended to achieve for clients.
-
E.
hadClientele
chosen
Indicates that an entity regularly served or catered to a particular group of clients or customers.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 27, 2026, 8:16 p.m.