Triple
T34886423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bill Cowley |
E1006155
|
entity |
| Predicate | notableTeamMate |
P2649
|
FINISHED |
| Object | Eddie Shore |
E61934
|
NE 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: Eddie Shore | Statement: [Bill Cowley, notableTeamMate, Eddie Shore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTeamMate Context triple: [Bill Cowley, notableTeamMate, Eddie Shore]
-
A.
notableTeammate
chosen
Indicates that one entity has a teammate relationship with another entity who is particularly prominent, distinguished, or noteworthy.
-
B.
notableOpponentTeamMember
Indicates that a specific team member is recognized as a particularly significant or noteworthy opponent in relation to another entity or context.
-
C.
notableTeamLeader
Indicates that an entity serves as a prominent or distinguished leader of a particular team.
-
D.
notableFriend
Indicates that one entity is a friend of another in a way that is especially prominent, well-known, or significant.
-
E.
notableMultipleTeamChampion
Indicates that an entity has won championship titles with multiple different teams.
- F. None of above.
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_69f76dbedb288190afe5780710847410 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3786d98bd081909f5552cbc2584537 |
completed | June 21, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.