Triple
T17332657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 America's Cup |
E420853
|
entity |
| Predicate | comebackFromScore |
P37419
|
FINISHED |
| Object | 1–8 |
—
|
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: 1–8 | Statement: [2013 America's Cup, comebackFromScore, 1–8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: comebackFromScore Context triple: [2013 America's Cup, comebackFromScore, 1–8]
-
A.
teamInComeback
Indicates that a team participates in or is responsible for a comeback, overturning a losing or disadvantaged position.
-
B.
decidingGameComebackWin
Indicates that a team or player secured a win in the final, decisive game of a series by overcoming a deficit and mounting a comeback.
-
C.
opponentInComeback
Indicates that an entity serves as the opposing side or competitor in a situation characterized as a comeback (e.g., recovering from a disadvantage).
-
D.
comebackContext
chosen
Indicates the situational background, circumstances, or prior events that frame or motivate a comeback or return.
-
E.
madeComeback
Indicates that an entity returned to a previous level of success, performance, or prominence after a period of decline, absence, or setback.
- 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_69d889d3adc881909319f1edb8d2a956 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a0fa57881909071fd395b3d46c4 |
completed | April 19, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69e3b021a5bc81909ae55406f9d0b37f |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:43 a.m.