Triple
T25086964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America's Cup 1980 |
E628349
|
entity |
| Predicate | challengerSailNumber |
P36730
|
FINISHED |
| Object | KA-5 |
—
|
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: KA-5 | Statement: [America's Cup 1980, challengerSailNumber, KA-5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: challengerSailNumber Context triple: [America's Cup 1980, challengerSailNumber, KA-5]
-
A.
sailNumber
chosen
Indicates the identifying number assigned to a specific sail or sailing vessel, typically used to distinguish it from others.
-
B.
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.
-
C.
challenger
Indicates that one entity is challenging or opposing another, typically by initiating a contest, dispute, or competitive confrontation.
-
D.
sailingSeries
Indicates a relationship where multiple sailing events or races are grouped together as part of the same organized series or competition.
-
E.
hullNumber
Indicates the unique identifying number assigned to the hull of a ship or vessel.
- 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_69f461e4d88c8190a81861b733d534ac |
completed | May 1, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:23 a.m.