Triple
T4358683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1974 Bob Dylan and The Band Tour |
E98611
|
entity |
| Predicate | returnAfterHiatusLength |
P12075
|
FINISHED |
| Object | 8 years |
—
|
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: 8 years | Statement: [1974 Bob Dylan and The Band Tour, returnAfterHiatusLength, 8 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnAfterHiatusLength Context triple: [1974 Bob Dylan and The Band Tour, returnAfterHiatusLength, 8 years]
-
A.
resumesAfter
Indicates that an activity, process, or state starts again following a pause, interruption, or completion of another specified event.
-
B.
interruptionDuration
chosen
Indicates the length of time for which an ongoing activity, process, or state is temporarily halted or disrupted.
-
C.
resumedIn
Indicates that an activity, process, or state that was previously paused or interrupted has started again within or at a specified context, time, or location.
-
D.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
E.
sessionLength
Indicates the duration of time that a particular session lasts from start to end.
- 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351e1bfa48190bb506d9ca1ed7b6a |
completed | March 12, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:16 p.m.