Triple
T34596132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NYYC |
E888313
|
entity |
| Predicate | roleInCompetition |
P33874
|
FINISHED |
| Object | founding defender of the America's Cup |
—
|
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: founding defender of the America's Cup | Statement: [NYYC, roleInCompetition, founding defender of the America's Cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInCompetition Context triple: [NYYC, roleInCompetition, founding defender of the America's Cup]
-
A.
competitionRole
chosen
Indicates that an entity holds a specific role, position, or function within a competitive event or contest.
-
B.
roleInRanking
Indicates that an entity holds a specific position or function within a particular ranking or ordered list.
-
C.
positionOnCompetition
Indicates the ranking or place an entity holds within the results of a specific competition.
-
D.
partnerInCompetition
Indicates that two or more entities are collaborating as partners or teammates within the same competitive event or context.
-
E.
competeIn
Indicates that an entity takes part as a contender in a particular event, activity, or domain where performance is compared against others.
- 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a00d15f7b788190a3bf440be7837192 |
completed | May 10, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_6a00d0f8ef548190b1c15b06164eec4a |
completed | May 10, 2026, 6:39 p.m. |
Created at: May 1, 2026, 2:03 a.m.