Triple
T34262832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humber Valley Golf Course |
E879081
|
entity |
| Predicate | greenFeePolicy |
P25908
|
FINISHED |
| Object | pay per round |
—
|
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: pay per round | Statement: [Humber Valley Golf Course, greenFeePolicy, pay per round]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: greenFeePolicy Context triple: [Humber Valley Golf Course, greenFeePolicy, pay per round]
-
A.
greenFeeLevel
Indicates the pricing tier or cost level associated with a green fee for using a golf course.
-
B.
feePolicy
chosen
Indicates the rules or conditions that determine how fees are calculated, applied, or charged in a given context.
-
C.
isFeePaying
Indicates that an entity is required to pay a fee in order to participate in, access, or receive a specified service, resource, or activity.
-
D.
fundingPolicy
Indicates the rules or guidelines governing how financial resources are allocated, distributed, or managed within a given context.
-
E.
feeUnit
Indicates the unit of measurement or currency in which a fee amount is expressed.
- 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_69f349b421cc8190b4b4655e1d612548 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:56 a.m.