Triple
T4222348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No Doubt |
E94369
|
entity |
| Predicate | hiatusPeriod |
P55400
|
FINISHED |
| Object | 2004–2008 |
—
|
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: 2004–2008 | Statement: [No Doubt, hiatusPeriod, 2004–2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hiatusPeriod Context triple: [No Doubt, hiatusPeriod, 2004–2008]
-
A.
hiatusLengthYears
Indicates the number of years between two related events or periods during which there is a break or interruption.
-
B.
hiatusBeforeRelease
Indicates that there is a pause or gap in activity occurring prior to a release event.
-
C.
heldAfter
Indicates that one event or state occurs or is maintained at some point in time after another specified event or state.
-
D.
holdsOver
Indicates that a certain condition, state, or relationship remains valid or continues to apply across a specified period, context, or range.
-
E.
heldWhen
Indicates that a particular state, condition, or relationship was true during a specified time or under certain temporal circumstances.
- F. None of above. chosen
Provenance (4 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_69b3451997e08190851db4a9a588837d |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34e4bf6088190926b982039a12079 |
completed | March 12, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69b347f1d7b48190bd8974c03c7dc937 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e4ace648190acf911853d4fcf86 |
completed | March 12, 2026, 11:37 p.m. |
Created at: March 12, 2026, 11:04 p.m.