Triple
T25086969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America's Cup 1980 |
E628349
|
entity |
| Predicate | winningYachtClub |
P45391
|
FINISHED |
| Object | New York Yacht Club |
—
|
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: New York Yacht Club | Statement: [America's Cup 1980, winningYachtClub, New York Yacht Club]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winningYachtClub Context triple: [America's Cup 1980, winningYachtClub, New York Yacht Club]
-
A.
hasYachtClub
Indicates that an entity possesses, hosts, or is associated with a yacht club.
-
B.
defendingYachtClub
Indicates that an entity is actively protecting or advocating for a yacht club against threats, criticism, or challenges.
-
C.
winnerClub
chosen
Indicates the club that has won a particular competition, match, or event.
-
D.
America’sCupChallenger
Indicates that an entity is a yacht club or team that formally challenges the defending holder for the America’s Cup sailing trophy.
-
E.
America’sCupDefender
Indicates that an entity serves as the defending title holder (the previous winner) in an America’s Cup sailing competition.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:23 a.m.