Triple
T1561064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tedy Bruschi |
E33323
|
entity |
| Predicate | returnedToPlayAfter |
P22128
|
FINISHED |
| Object | stroke in 2005 |
—
|
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: stroke in 2005 | Statement: [Tedy Bruschi, returnedToPlayAfter, stroke in 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedToPlayAfter Context triple: [Tedy Bruschi, returnedToPlayAfter, stroke in 2005]
-
A.
returnedToPlayAfterIllness
chosen
Indicates that an entity resumed participating in play or competition after having been sidelined due to an illness.
-
B.
inningsPlayed
Indicates the number of innings in which an entity (typically a player or team) has participated during a game or season.
-
C.
eraPlayed
Indicates the historical or stylistic time period during which something (typically a work or performance) was played or took place.
-
D.
playedUntil
Indicates that an action or event involving playing continued up to a specific time, point, or condition.
-
E.
returnedFromRetirement
Indicates that an entity has resumed an activity, role, or position after having previously retired from it.
- 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_69a885ef9cf48190b0af0f5ce3d02231 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9407d9d1481909597af97b16512cc |
completed | March 5, 2026, 8:36 a.m. |
| PD | Predicate disambiguation | batch_69a907b688d081908171f89010c53973 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:27 p.m.