Triple
T31204846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal and Ancient Golf Club of St Andrews |
E795573
|
entity |
| Predicate | governedRulesOf |
P91355
|
FINISHED |
| Object | golf |
—
|
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 | Statement: [Royal and Ancient Golf Club of St Andrews, governedRulesOf, golf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedRulesOf Context triple: [Royal and Ancient Golf Club of St Andrews, governedRulesOf, golf]
-
A.
isRuleGoverned
Indicates that an entity’s behavior, structure, or operation is determined and constrained by explicit rules or formal regulations.
-
B.
rulesBy
chosen
Indicates that one entity governs, controls, or exercises authoritative power over another entity.
-
C.
governingJurisdictionForRules
Indicates the legal or regulatory jurisdiction under whose authority a given set of rules or regulations applies.
-
D.
governedFor
Indicates that one entity exercised governing authority or administrative control on behalf of, or in the interest of, another entity.
-
E.
governedInPartBy
Indicates that something is subject to the authority, control, or influence of a governing entity, but only to a limited or partial extent rather than fully.
- 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_69f224d8c6608190b7882466521f62be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffb69812808190a751853b30183e65 |
completed | May 9, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69ffb63bdda88190a9dd8426dc0bad43 |
completed | May 9, 2026, 10:33 p.m. |
Created at: April 29, 2026, 9:09 p.m.