Triple
T17299757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America’s Cup |
E420009
|
entity |
| Predicate | longestWinningStreakEnd |
P126883
|
FINISHED |
| Object | 1983 |
—
|
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: 1983 | Statement: [America’s Cup, longestWinningStreakEnd, 1983]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: longestWinningStreakEnd Context triple: [America’s Cup, longestWinningStreakEnd, 1983]
-
A.
hittingStreakEndDate
Indicates the date on which a continuous sequence of successful hits or performances comes to an end.
-
B.
longestUnbeatenStreak
Indicates the relationship where an entity holds the greatest continuous sequence of events (such as games or matches) without a loss compared to others.
-
C.
consecutiveGamesStreakEndSeason
Indicates the season in which an entity’s streak of playing in consecutive games comes to an end.
-
D.
consecutiveGamesRecordHeldUntil
Indicates that an entity held the record for most consecutive games until a specified later point in time or event.
-
E.
mostConsecutiveWinsCount
Indicates the highest number of wins achieved in a row within a given sequence or context.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e438f9e5ac8190ba0b5820790112d9 |
completed | April 19, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:41 a.m.