Triple
T25556709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shawn Michaels |
E640590
|
entity |
| Predicate | temporaryReturn |
P17857
|
FINISHED |
| Object | 2018-11-02 |
—
|
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: 2018-11-02 | Statement: [Shawn Michaels, temporaryReturn, 2018-11-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: temporaryReturn Context triple: [Shawn Michaels, temporaryReturn, 2018-11-02]
-
A.
temporaryClosure
Indicates that an entity is closed or unavailable for a limited, non-permanent period of time.
-
B.
temporaryControl
Indicates that one entity has non-permanent, time-limited authority or influence over another entity or resource.
-
C.
temporaryLocation
Indicates that an entity is located at a place for a limited or non-permanent duration.
-
D.
temporaryOutcome
Indicates that a result or state produced by an action or process is provisional and expected to change or be replaced later.
-
E.
temporaryRetirement
chosen
Indicates a state in which an entity has withdrawn from its usual role or activity for a limited period, with the expectation of returning later.
- 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_69e75dc101a881909fd33b02174e9768 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f8ca2cf48190997cd68875571217 |
completed | May 2, 2026, 1:14 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 3:40 p.m.