Triple
T34884443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rotana Hotels & Resorts |
E1006103
|
entity |
| Predicate | hasNotablePropertyIn |
P204219
|
FINISHED |
| Object | Dubai |
E3323
|
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: Dubai | Statement: [Rotana Hotels & Resorts, hasNotablePropertyIn, Dubai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotablePropertyIn Context triple: [Rotana Hotels & Resorts, hasNotablePropertyIn, Dubai]
-
A.
hasNotablePropertyNamedAfter
Indicates that an entity possesses a notable property or attribute that is named in honor of, or derived from, another entity.
-
B.
haveProperty
Indicates that an entity possesses, exhibits, or is characterized by a particular property or attribute.
-
C.
hasNotabilityFor
Indicates that an entity is notable, recognized, or significant specifically in relation to a given subject, context, or domain.
-
D.
hasNotableItem
Indicates that an entity possesses, contains, or is associated with an item considered notable or significant in some context.
-
E.
propertyContained
Indicates that one property or attribute is fully included within, or is a subset of, another property or attribute.
- F. None of above. chosen
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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a034af7066c81908719bff353d77b16 |
completed | May 12, 2026, 3:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37b25de02c8190956d5698dbabf474 |
completed | June 21, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_6a034a2fc2308190b0b8fbd458a39323 |
completed | May 12, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_6a034af656d88190881820908f6d2958 |
completed | May 12, 2026, 3:44 p.m. |
Created at: May 3, 2026, 4 p.m.