Triple
T22125583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Don't Forget |
E546782
|
entity |
| Predicate | previousWorkInChronology |
P22762
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [Don't Forget, previousWorkInChronology, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousWorkInChronology Context triple: [Don't Forget, previousWorkInChronology, none]
-
A.
previousWorkInSeries
Indicates that one work directly precedes another within the same series or sequence.
-
B.
previousWorkAfterHiatusOf
Indicates that one work directly follows and resumes activity after a hiatus or break from a previous work.
-
C.
previousWorkGap
Indicates a period of time during which an entity had no prior work or employment between two work-related events or positions.
-
D.
previousWorkByProducer
Indicates that a work was created earlier by the same producer responsible for another referenced work.
-
E.
chronologyPrevious
chosen
Indicates that one event, item, or state occurs directly before another in a chronological sequence.
- 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12980e2488190b58b541c8bee8480 |
completed | April 28, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:31 p.m.