Triple
T25086972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America's Cup 1980 |
E628349
|
entity |
| Predicate | trophyDefended |
P157625
|
FINISHED |
| Object | America's Cup |
—
|
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: America's Cup | Statement: [America's Cup 1980, trophyDefended, America's Cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trophyDefended Context triple: [America's Cup 1980, trophyDefended, America's Cup]
-
A.
trophy
Indicates that one entity is a trophy awarded or possessed in relation to another entity, typically as a result of winning or achieving something.
-
B.
trophyCustodian
Indicates that one entity is responsible for holding, safeguarding, or managing a trophy on behalf of another entity or organization.
-
C.
awardedToDefenders
Indicates that something (such as a title, honor, or recognition) is granted specifically to entities serving in a defensive role.
-
D.
trophyContestedBy
Indicates that a particular trophy is the object of competition among the specified participants or teams.
-
E.
canBeDefendedIn
Indicates that something (such as a claim, action, or position) is capable of being justified or supported within a specified context, forum, or framework.
- 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_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_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
| PDg | Predicate description generation | batch_69f448fe11f08190bdd53ca7ba2d51e4 |
completed | May 1, 2026, 6:32 a.m. |
Created at: April 18, 2026, 6:23 a.m.