Triple
T3020190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tommy Morrison |
E82434
|
entity |
| Predicate | attemptedComeback |
P26503
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Tommy Morrison, attemptedComeback, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attemptedComeback Context triple: [Tommy Morrison, attemptedComeback, 2007]
-
A.
attemptedComebackSeason
chosen
Indicates that an entity made an effort to return to a previous level of performance or prominence after a period of decline or absence.
-
B.
teamInComeback
Indicates that a team participates in or is responsible for a comeback, overturning a losing or disadvantaged position.
-
C.
opponentInComeback
Indicates that an entity serves as the opposing side or competitor in a situation characterized as a comeback (e.g., recovering from a disadvantage).
-
D.
attemptedRestoration
Indicates an action where an entity makes an effort to restore or return another entity to a previous or desired state, condition, or form, regardless of whether the restoration succeeds.
-
E.
wasTriedAt
Indicates that a legal case or judicial proceeding involving an entity took place at a specific court or location.
- 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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a940c048190bc46e2c8001db8c0 |
completed | March 8, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69ad961c430c8190ac48f2e3c7e7c649 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.