Triple
T35807346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adam Joseph Copeland |
E1035133
|
entity |
| Predicate | retirementFromWrestling |
P87622
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Adam Joseph Copeland, retirementFromWrestling, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retirementFromWrestling Context triple: [Adam Joseph Copeland, retirementFromWrestling, 2011]
-
A.
wrestlingRetirement
chosen
Indicates that an individual has ended or formally withdrawn from participating in professional wrestling competition.
-
B.
retiredFromSidelines
Indicates that an entity has ended its role or involvement from a previously inactive, observing, or non-participatory position in a given context.
-
C.
announcedRetirementFrom
Indicates that an entity has publicly declared its intention to retire from a particular role, position, organization, or activity.
-
D.
announcedRetirementBy
Indicates that one party has publicly declared the retirement of another party.
-
E.
retiredFrom
Indicates that an entity has permanently stopped working for or being active in a specified organization, role, or activity.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:06 p.m.