Triple
T36346875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States national golf team |
E895087
|
entity |
| Predicate | PresidentsCupFormat |
P185411
|
FINISHED |
| Object | match play |
—
|
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: match play | Statement: [United States national golf team, PresidentsCupFormat, match play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PresidentsCupFormat Context triple: [United States national golf team, PresidentsCupFormat, match play]
-
A.
RyderCupFormat
Indicates the competitive structure, rules, and match-play arrangement used in the Ryder Cup golf event.
-
B.
presidentsCupTitle
Indicates that an entity has won or holds the title of the Presidents Cup in a given competition or context.
-
C.
PresidentsCupAppearance
Indicates that an entity has participated in or made an appearance at the Presidents Cup golf competition.
-
D.
worldCupFormat
Indicates the specific structure, rules, and progression system used to organize and play a given World Cup competition.
-
E.
finalsSeriesFormat
Indicates the specific structure or rules governing how a finals series is organized and played (e.g., number of games, sequence, and format).
- F. None of above. chosen
Provenance (4 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be9b9ab481908328e0e8d8ac73d4 |
completed | May 3, 2026, 9:31 p.m. |
Created at: May 3, 2026, 4:09 p.m.