Triple
T32723350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QB: My Life Behind the Spiral |
E836734
|
entity |
| Predicate | notableTeamMentioned |
P69211
|
FINISHED |
| Object | San Francisco 49ers |
E34954
|
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: San Francisco 49ers | Statement: [QB: My Life Behind the Spiral, notableTeamMentioned, San Francisco 49ers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTeamMentioned Context triple: [QB: My Life Behind the Spiral, notableTeamMentioned, San Francisco 49ers]
-
A.
notableTeamType
Indicates that an entity is notably associated with a team of a specified type (e.g., national team, club team, or other team category).
-
B.
notableTeams
chosen
Indicates that there is a noteworthy association between an entity and one or more teams with which it is significantly connected or recognized.
-
C.
notableChampionTeam
Indicates that a team is notably recognized as the champion associated with a particular competition, event, or context.
-
D.
notableEventTeam
Indicates a team that is significantly associated with, or played a key role in, a particular notable event.
-
E.
notablePlayerTeam1
Indicates that the referenced player is a notable or prominent member of the first team in a given context or matchup.
- 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_69f34935455881909088975d79460418 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34a7a68808819090492253a6c3f50b |
completed | June 19, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:11 a.m.