Triple
T35210454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1992 America’s Cup |
E1016658
|
entity |
| Predicate | defenderSelectionWinner |
P2688
|
FINISHED |
| Object | America3 |
—
|
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: America3 | Statement: [1992 America’s Cup, defenderSelectionWinner, America3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defenderSelectionWinner Context triple: [1992 America’s Cup, defenderSelectionWinner, America3]
-
A.
awardedToDefenders
Indicates that something (such as a title, honor, or recognition) is granted specifically to entities serving in a defensive role.
-
B.
defenderIn
Indicates that an entity serves as a defensive agent or protector within a specified context, situation, or domain.
-
C.
defendingChampion
chosen
Indicates that an entity currently holds a title or championship and is defending it against challengers.
-
D.
defender
Indicates a relationship where one entity protects, guards, or supports another entity against threats, attacks, or criticism.
-
E.
defendingRaceWinner
Indicates that an entity is the current titleholder who won the previous edition of a race and is thus defending that victory in the present event.
- 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_69f76ddf549c8190869d0af076fd2c28 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:02 p.m.