Triple
T2117732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfred Dunhill Links Championship |
E43845
|
entity |
| Predicate | teamCompetition |
P15194
|
FINISHED |
| Object | professional–amateur teams |
—
|
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: professional–amateur teams | Statement: [Alfred Dunhill Links Championship, teamCompetition, professional–amateur teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamCompetition Context triple: [Alfred Dunhill Links Championship, teamCompetition, professional–amateur teams]
-
A.
memberTeam
Indicates that an entity belongs to or is part of a specific team.
-
B.
teamAchievement
Indicates that a group of individuals collectively accomplished a shared goal or met a performance milestone.
-
C.
rivalTeam
Indicates that one team is in a competitive or adversarial relationship with another team, often vying for superiority or dominance.
-
D.
teamParticipated
chosen
Indicates that a team took part in or was involved in a particular event, activity, or competition.
-
E.
associatedTeam
Indicates that one entity is linked or connected to a particular team, typically as its member, owner, or primary affiliation.
- 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_69a88717cfe48190b7ecdd68c824848a |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb2f6f608190937889bb393fe7c6 |
completed | March 7, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69abb7bbf9d881909d223b0cab7cab18 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.