Triple
T9871886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prestwick Golf Club |
E239975
|
entity |
| Predicate | allowsVisitorPlay |
P32554
|
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: [Prestwick Golf Club, allowsVisitorPlay, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsVisitorPlay Context triple: [Prestwick Golf Club, allowsVisitorPlay, yes]
-
A.
allowsPlayerAction
Indicates that one entity permits or enables a player to perform a specific action within a system or context.
-
B.
canVisit
chosen
Indicates that one entity is permitted or able to go to or access another entity or location.
-
C.
allowsForeignPlayers
Indicates that an entity permits participation or involvement by players who are from foreign countries or outside its primary jurisdiction.
-
D.
spectatorRestrictions
Indicates limitations, conditions, or rules governing who may be present as spectators and under what circumstances.
-
E.
kickingAllowed
Indicates that performing or engaging in kicking is permitted within the specified context or under the given conditions.
- 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_69ca84e8a0788190b9061811d50fd554 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3f5cc948190b03186b867c92229 |
completed | April 2, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69cd1d7621d48190aa6a6f34399514b0 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:36 p.m.