Triple
T9242620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Troon Yacht Haven |
E222099
|
entity |
| Predicate | cateringFacility |
P44773
|
FINISHED |
| Object | on‑site bar and restaurant |
—
|
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: on‑site bar and restaurant | Statement: [Troon Yacht Haven, cateringFacility, on‑site bar and restaurant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cateringFacility Context triple: [Troon Yacht Haven, cateringFacility, on‑site bar and restaurant]
-
A.
servesVenue
Indicates that an entity provides services or functions in support of a particular venue.
-
B.
alsoEats
Indicates that an entity consumes something in addition to another item or items it already eats.
-
C.
servesFacility
Indicates that one entity provides services or support to a particular facility as its client, target, or area of operation.
-
D.
cateringIncludes
chosen
Indicates that a catering service or arrangement encompasses or provides the specified item, service, or component as part of its offering.
-
E.
restaurantDesignedBy
Indicates that a restaurant was created or planned by a particular designer or architect.
- 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_69ca83ee26cc81909ac624e190597d6d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cd03ec23ec8190993003a826372d40 |
completed | April 1, 2026, 11:39 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4765648190aa9445c4a22dc471 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:30 p.m.