Triple
T20104310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joe Frazier |
E181401
|
entity |
| Predicate | briefComeback |
P94430
|
FINISHED |
| Object | 1981 |
—
|
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: 1981 | Statement: [Joe Frazier, briefComeback, 1981]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: briefComeback Context triple: [Joe Frazier, briefComeback, 1981]
-
A.
madeComeback
chosen
Indicates that an entity returned to a previous level of success, performance, or prominence after a period of decline, absence, or setback.
-
B.
comebackContext
Indicates the situational background, circumstances, or prior events that frame or motivate a comeback or return.
-
C.
comebackSingleFor
Indicates that a particular single serves as a comeback release for an artist or group, marking their return after a hiatus or previous work.
-
D.
comebackWorkFor
Indicates that an entity returns to a previous workplace or employer to work again.
-
E.
broughtBack
Indicates that an entity caused another entity to return to a previous place, state, or condition.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666daf73c819089f02ca6faa2c283 |
completed | April 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:27 p.m.