Triple
T23323162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Musselburgh Old Course |
E591211
|
entity |
| Predicate | greenFeeRequired |
P68080
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Musselburgh Old Course, greenFeeRequired, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: greenFeeRequired Context triple: [Musselburgh Old Course, greenFeeRequired, true]
-
A.
greenFeeLevel
Indicates the pricing tier or cost level associated with a green fee for using a golf course.
-
B.
feeRequirement
Indicates that a payment or fee must be provided or satisfied as a condition for a particular action, service, or relationship to occur or remain valid.
-
C.
isFeePaying
chosen
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.
chargesFeeFor
Indicates that one entity requires payment of a fee from another entity in exchange for a specific service, product, or privilege.
-
E.
retrievalFee
Indicates the fee charged for retrieving or accessing an item, resource, or information.
- 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_69e25d1effe4819096907f95f610dbff |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1978731b0819090f92ef768f2a749 |
completed | April 29, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:07 p.m.