Triple
T36896484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plantation Course |
E911902
|
entity |
| Predicate | isRecreationFacilityType |
P186657
|
FINISHED |
| Object | golf facility |
—
|
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: golf facility | Statement: [Plantation Course, isRecreationFacilityType, golf facility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRecreationFacilityType Context triple: [Plantation Course, isRecreationFacilityType, golf facility]
-
A.
isRecreationalFacility
Indicates that the subject entity functions as a place or installation intended for leisure, sports, or other recreational activities.
-
B.
hasRecreationFacility
Indicates that one entity provides, contains, or is equipped with a recreational facility for use by another entity or by the public.
-
C.
isRecreationalResourceFor
Indicates that something serves as a facility, area, or service used by someone for leisure, recreation, or enjoyment.
-
D.
isRecreationalArea
Indicates that a place or space is designated and used primarily for leisure, relaxation, or recreational activities.
-
E.
recreationActivitiesSupported
Indicates that an entity provides, allows, or is compatible with certain recreational activities.
- F. None of above. chosen
Provenance (4 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_69f76e841b54819097e7fa768bbc70b2 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:13 p.m.