Triple
T17668959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worcester Country Club |
E440461
|
entity |
| Predicate | hasNotableEventRole |
P17461
|
FINISHED |
| Object | host of first Ryder Cup on American soil |
—
|
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: host of first Ryder Cup on American soil | Statement: [Worcester Country Club, hasNotableEventRole, host of first Ryder Cup on American soil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableEventRole Context triple: [Worcester Country Club, hasNotableEventRole, host of first Ryder Cup on American soil]
-
A.
hasNotableRoleIn
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
-
B.
hasNotablePersonEvent
Indicates that there exists a significant event in which the person plays a notable or central role.
-
C.
hasNotableEventName
Indicates that an entity is associated with a notable event identified by a specific name.
-
D.
significantEventRole
chosen
Indicates that an entity plays an important or defining role in a particular significant event.
-
E.
hasNotableShow
Indicates that an entity is associated with a particular show that is considered notable or significant.
- 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f6723d081908eaa57eef6d70bd0 |
completed | April 19, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69e3cde007d8819090dd92eea9f022cc |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 9:58 a.m.