Triple
T23551598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pendulum |
E578062
|
entity |
| Predicate | returnedFromHiatus |
P150215
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Pendulum, returnedFromHiatus, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedFromHiatus Context triple: [Pendulum, returnedFromHiatus, 2016]
-
A.
releasedAfterHiatusOf
chosen
Indicates that one entity (typically a work or product) was released following a preceding break or hiatus of the other entity (such as an artist, series, or organization).
-
B.
returnedFrom
Indicates that an entity has come back or been sent back from a specified source, location, or prior state.
-
C.
returnedFromRetirement
Indicates that an entity has resumed an activity, role, or position after having previously retired from it.
-
D.
returnedDuring
Indicates that one entity was given back or restored to another entity within a specified time period or event.
-
E.
returnedToLiveIn
Indicates that an entity moved back to a place where they had previously lived and resumed living there.
- 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_69e245fa93448190919cb04534560542 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1aecf28508190b8d3396591e5e6bb |
completed | April 29, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:11 p.m.