Triple
T17299755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America’s Cup |
E420009
|
entity |
| Predicate | longestWinningStreakDuration |
P121028
|
FINISHED |
| Object | 132 years |
—
|
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: 132 years | Statement: [America’s Cup, longestWinningStreakDuration, 132 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: longestWinningStreakDuration Context triple: [America’s Cup, longestWinningStreakDuration, 132 years]
-
A.
mostConsecutiveWinsCount
Indicates the highest number of wins achieved in a row within a given sequence or context.
-
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.
unbeatenStreakLength
chosen
Indicates the length of a continuous sequence during which an entity has not been defeated or has remained without a loss.
-
D.
consecutiveGamesRecordHeldFrom
Indicates that one entity held the record for most consecutive games played starting from a specified point in time.
-
E.
mostRuns
Indicates that one entity has scored a greater number of runs than all comparable entities in a given context or set.
- 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_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. |
Created at: April 10, 2026, 5:41 a.m.