Triple
T33769633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martin St. Louis |
E865339
|
entity |
| Predicate | primaryTeamInPrime |
P206666
|
FINISHED |
| Object | Tampa Bay Lightning |
E15849
|
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: Tampa Bay Lightning | Statement: [Martin St. Louis, primaryTeamInPrime, Tampa Bay Lightning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryTeamInPrime Context triple: [Martin St. Louis, primaryTeamInPrime, Tampa Bay Lightning]
-
A.
primaryTeam
Indicates that one entity is the main or principal team associated with another entity, such as a person, project, or organization.
-
B.
primaryTeams
Indicates that one or more teams are the main or principal teams associated with a given entity.
-
C.
primaryTeamBrand
Indicates the brand or franchise that serves as an entity’s main or primary team affiliation.
-
D.
primaryTeamState
Indicates the state or status currently associated with an entity’s primary team.
-
E.
primaryTeamHosted
Indicates that the primary team served as the host (home side) for the event or matchup involving the related entity.
- F. None of above. chosen
Provenance (5 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a368226fe8c819099a2b332baab128a |
completed | June 20, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037e07fe4481909ca21eae7a941ee7 |
completed | May 12, 2026, 7:22 p.m. |
Created at: May 1, 2026, 1:45 a.m.