Triple
T3070790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Cinque Ports Golf Club |
E64013
|
entity |
| Predicate | practiceFacilities |
P17072
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Royal Cinque Ports Golf Club, practiceFacilities, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: practiceFacilities Context triple: [Royal Cinque Ports Golf Club, practiceFacilities, yes]
-
A.
practiceFacility
chosen
Indicates that a location serves as a facility where individuals or groups regularly practice a particular activity, skill, or sport.
-
B.
facility
Indicates that one entity is a building, installation, or physical infrastructure used to host, support, or enable the operations or activities of another entity.
-
C.
practiceElement
Indicates that one entity is a component, step, or sub-activity within a broader practice or procedure involving another entity.
-
D.
servesFacility
Indicates that one entity provides services or support to a particular facility as its client, target, or area of operation.
-
E.
userFacility
Indicates a relationship where a user is associated with, has access to, or operates within a particular facility.
- 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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada14b366881908e2ca104e5f38251 |
completed | March 8, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69ad9625b30c819099ef9349c91d7b25 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.