Triple
T27510305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Amateur Public Links Championship |
E694389
|
entity |
| Predicate | establishedToServe |
P42835
|
FINISHED |
| Object | public-course golfers |
—
|
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: public-course golfers | Statement: [U.S. Amateur Public Links Championship, establishedToServe, public-course golfers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedToServe Context triple: [U.S. Amateur Public Links Championship, establishedToServe, public-course golfers]
-
A.
establishedAs
Indicates that one entity is formally created, designated, or recognized in a particular role, status, or identity as another entity.
-
B.
establishedTo
chosen
Indicates that one entity was created, founded, or set up for the purpose of serving, supporting, or enabling another entity.
-
C.
mayServe
Indicates that one entity is permitted or authorized to provide a service or function to another entity.
-
D.
isServed
Indicates that one entity provides or delivers a service, product, or assistance to another entity.
-
E.
isServedAt
Indicates that something (such as food, drink, or a service) is provided or made available at a particular place or venue.
- 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 27, 2026, 1:15 p.m.