Triple
T31186178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Amateur |
E795049
|
entity |
| Predicate | governingRulesAuthority |
P18774
|
FINISHED |
| Object | The R&A |
—
|
NE NERFINISHED |
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: The R&A | Statement: [The Amateur, governingRulesAuthority, The R&A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingRulesAuthority Context triple: [The Amateur, governingRulesAuthority, The R&A]
-
A.
governingBodyForRules
chosen
Indicates that an entity serves as the official authority responsible for creating, maintaining, or enforcing a specified set of rules.
-
B.
governingJurisdictionForRules
Indicates the legal or regulatory jurisdiction under whose authority a given set of rules or regulations applies.
-
C.
areGovernedBy
Indicates that one or more entities are under the authority, control, or administration of a governing body or ruler.
-
D.
governingElectionAuthority
Indicates the authority or body responsible for organizing, overseeing, and regulating a particular election.
-
E.
lawGovernedBy
Indicates that the application, interpretation, or enforcement of a law is determined or controlled by a particular legal authority, jurisdiction, or legal system.
- 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_69f224d675d08190957198068e440422 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffb5c373948190a6606e8caa87a384 |
completed | May 9, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69ffb261da788190b41399df8ed895e8 |
completed | May 9, 2026, 10:17 p.m. |
Created at: April 29, 2026, 9:08 p.m.