Triple
T13575966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selke Trophy |
E324285
|
entity |
| Predicate | associatedStatistic |
P3976
|
FINISHED |
| Object | plus-minus |
—
|
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: plus-minus | Statement: [Selke Trophy, associatedStatistic, plus-minus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedStatistic Context triple: [Selke Trophy, associatedStatistic, plus-minus]
-
A.
hasStatistics
chosen
Indicates that an entity is associated with one or more statistical measures, records, or summaries describing its quantitative properties or performance.
-
B.
statisticsConsidered
Indicates that certain statistics are taken into account or used as a basis in a decision, analysis, or evaluation involving the related entities.
-
C.
statisticNote
Indicates that there is an explanatory note or comment providing additional context or clarification about a reported statistic.
-
D.
relatedMetric
Indicates that one metric has a defined relationship or dependency with another metric.
-
E.
statValue
Indicates that an entity has a particular statistical attribute with a specified value.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb02b1f108190a12af382d1de70bb |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.