Triple
T18752216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riffa Golf Club |
E458552
|
entity |
| Predicate | amenityFeature |
P124384
|
FINISHED |
| Object | dining options |
—
|
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: dining options | Statement: [Riffa Golf Club, amenityFeature, dining options]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: amenityFeature Context triple: [Riffa Golf Club, amenityFeature, dining options]
-
A.
amenity
Indicates that one entity provides a useful facility, service, or feature that enhances the convenience or comfort of another entity.
-
B.
typicalAmenity
chosen
Indicates that something is a common or characteristic amenity typically associated with a given entity or context.
-
C.
amenityFocus
Indicates a relationship where an amenity is specifically oriented toward, designed for, or primarily serving a particular focus or target (such as a user group, activity, or purpose).
-
D.
amenityLevel
Indicates the degree or quality of facilities, services, or conveniences provided in relation to something.
-
E.
hasCivicAmenity
Indicates that an entity possesses, provides, or is associated with a public facility or service intended for community use.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579ee4194819089661132f9f0f849 |
completed | April 20, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.