Triple
T17332653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 America's Cup |
E420853
|
entity |
| Predicate | reasonExtraRaces |
P55607
|
FINISHED |
| Object | penalty to Oracle Team USA |
—
|
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: penalty to Oracle Team USA | Statement: [2013 America's Cup, reasonExtraRaces, penalty to Oracle Team USA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonExtraRaces Context triple: [2013 America's Cup, reasonExtraRaces, penalty to Oracle Team USA]
-
A.
relatedRace
Indicates that there is a connection or association between two races, such as similarity, relevance, or contextual linkage.
-
B.
rarityReason
Indicates the underlying cause or justification for why something is considered rare.
-
C.
hasSupportRaces
Indicates that an entity provides backing, endorsement, or assistance to one or more races (such as competitions or racial groups).
-
D.
roleInRaces
Indicates the specific capacity or function an entity has within one or more races or racing events.
-
E.
reasonForSpecialMeasures
chosen
Indicates that one entity specifies the justification or cause for which special measures or exceptional actions are taken regarding another entity.
- 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.