Triple
T17332654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 America's Cup |
E420853
|
entity |
| Predicate | penaltyPoints |
P127041
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [2013 America's Cup, penaltyPoints, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: penaltyPoints Context triple: [2013 America's Cup, penaltyPoints, 2]
-
A.
penaltyMechanism
Indicates a relationship where a rule, system, or process imposes a negative consequence or sanction in response to certain actions or conditions.
-
B.
defaultPenalty
Indicates that a standard or automatically applied penalty is imposed in the absence of a specific or overridden penalty.
-
C.
penaltiesAdjustedBy
Indicates that one entity’s penalties are modified, recalculated, or otherwise changed as a result of another entity’s influence or action.
-
D.
penaltyScoredBy
Indicates that a penalty (typically in a game or sport) was successfully converted or scored by a particular participant.
-
E.
penaltyGoalPoints
Indicates that points are awarded for a goal scored from a penalty situation.
- 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_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. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:43 a.m.