Triple
T9237318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Time Jumpers |
E221969
|
entity |
| Predicate | regularPerformanceDay |
P34404
|
FINISHED |
| Object | Monday night |
—
|
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: Monday night | Statement: [The Time Jumpers, regularPerformanceDay, Monday night]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularPerformanceDay Context triple: [The Time Jumpers, regularPerformanceDay, Monday night]
-
A.
typicalEventDay
chosen
Indicates the day on which an event is normally or most commonly held or occurs.
-
B.
regularCategory
Indicates that a category satisfies the additional structural conditions required to be considered a “regular” category, typically involving stable image factorizations and certain pullback properties.
-
C.
peakDay
Indicates the specific day on which a quantity, activity, or effect reaches its maximum level within a given period.
-
D.
weekdayServicePattern
Indicates a service pattern or schedule that specifically applies on weekdays rather than weekends or holidays.
-
E.
notableRoutine
Indicates a routine, practice, or sequence of actions that is especially prominent, well-known, or significant in some context.
- 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_69ca83ed628c8190bc02d641e57f097f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccf09e553081909cf864635cfc5dcc |
completed | April 1, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4765648190aa9445c4a22dc471 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:29 p.m.