Triple
T32663836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 Walker Cup team |
E835100
|
entity |
| Predicate | previousEditionTeam |
P198062
|
FINISHED |
| Object | 2017 United States Walker Cup team |
—
|
NE NERFINISHED |
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: 2017 United States Walker Cup team | Statement: [2019 Walker Cup team, previousEditionTeam, 2017 United States Walker Cup team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousEditionTeam Context triple: [2019 Walker Cup team, previousEditionTeam, 2017 United States Walker Cup team]
-
A.
lastEditionTeams
Indicates that the related teams participated in the most recent edition of a given competition or event.
-
B.
predecessorTeamOf
Indicates that one team previously existed in a role or capacity that was later taken over or continued by another team.
-
C.
formerTeam2Name
Indicates that an entity was previously associated with a second former team identified by this name.
-
D.
homeTeamPreviousTitleSeason
Indicates the season in which the home team most recently won a title prior to the current event or season.
-
E.
team1LaterKnownAs
Indicates that the first team was later renamed to or became known by the identity of the second team.
- 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_69f349303ccc8190a70d0f6e8a21d3fb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fec5c503808190bde0b1829ea43071 |
completed | May 9, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69fec535dd6c8190a6ab85201f5a04a9 |
completed | May 9, 2026, 5:25 a.m. |
| PDg | Predicate description generation | batch_69fec5c3f8248190b835a8e4eba470c4 |
completed | May 9, 2026, 5:27 a.m. |
Created at: May 1, 2026, 1:08 a.m.