Triple
T11492597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zach Parise |
E272451
|
entity |
| Predicate | contractDetail |
P87081
|
FINISHED |
| Object | 13-year contract with Minnesota Wild in 2012 |
—
|
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: 13-year contract with Minnesota Wild in 2012 | Statement: [Zach Parise, contractDetail, 13-year contract with Minnesota Wild in 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contractDetail Context triple: [Zach Parise, contractDetail, 13-year contract with Minnesota Wild in 2012]
-
A.
contractValue
Indicates the monetary worth or agreed-upon financial amount specified in a contract between parties.
-
B.
contractFeature
Indicates that one entity is a feature, term, or provision that is included in or associated with a particular contract.
-
C.
contractUnit
Indicates that one entity serves as a contractual unit or party within a contract relationship involving another entity.
-
D.
legalDetail
Indicates that there is specific legal information, conditions, or attributes associated with the related entity or relationship.
-
E.
dealContent
chosen
Indicates that one entity contains, specifies, or represents the substantive terms, details, or material of a deal or agreement involving 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_69d6aae1b09881909ce2ded3fa0c14fa |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d85a21fb048190acb0960aefd4fe0a |
completed | April 10, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69d808736c5c8190899b5b3b2e797f65 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:36 p.m.