Triple
T25030581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnny Gaudreau |
E626829
|
entity |
| Predicate | notableForTeam |
P3211
|
FINISHED |
| Object | Calgary Flames top-line winger |
—
|
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: Calgary Flames top-line winger | Statement: [Johnny Gaudreau, notableForTeam, Calgary Flames top-line winger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableForTeam Context triple: [Johnny Gaudreau, notableForTeam, Calgary Flames top-line winger]
-
A.
notableTeammate
Indicates that one entity has a teammate relationship with another entity who is particularly prominent, distinguished, or noteworthy.
-
B.
notableTeamLeader
Indicates that an entity serves as a prominent or distinguished leader of a particular team.
-
C.
teamInNotableGame
Indicates that a team participated as one of the competitors in a game or match considered notable or significant.
-
D.
notablePlayerTeam1
chosen
Indicates that the referenced player is a notable or prominent member of the first team in a given context or matchup.
-
E.
notableTeamPublished
Indicates that a team is recognized as notably responsible for publishing or releasing a particular work or result.
- 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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 18, 2026, 6:07 a.m.