Triple
T34898406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanley Cup Finals games |
E1006505
|
entity |
| Predicate | historicallyPlayedBy |
P202548
|
FINISHED |
| Object | NHL champion |
—
|
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: NHL champion | Statement: [Stanley Cup Finals games, historicallyPlayedBy, NHL champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyPlayedBy Context triple: [Stanley Cup Finals games, historicallyPlayedBy, NHL champion]
-
A.
oftenPlayedBy
Indicates that one entity frequently performs, portrays, or executes another entity, such as a role, character, or piece of music.
-
B.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
C.
portrayedBySince
Indicates that an entity has been portrayed by a particular actor or performer starting from a specified point in time and continuing thereafter.
-
D.
arePlayedBy
Indicates that one or more performers (such as actors or musicians) carry out, interpret, or execute the referenced roles, characters, or pieces.
-
E.
laterPortrayedBy
Indicates that an entity is subsequently depicted or played by another entity in a later work or time.
- 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_69f76dbfe5788190ad8b64f241f470c8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a008ebb22408190a2293bced40a7e53 |
completed | May 10, 2026, 1:57 p.m. |
| PD | Predicate disambiguation | batch_6a008e8715dc8190ab23292605901bf4 |
completed | May 10, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_6a008eba6de8819083165152448f6071 |
completed | May 10, 2026, 1:57 p.m. |
Created at: May 3, 2026, 4 p.m.