Triple
T21489144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Village Vanguard |
E530189
|
entity |
| Predicate | typicalShowSchedule |
P3309
|
FINISHED |
| Object | seven nights a week |
—
|
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: seven nights a week | Statement: [Village Vanguard, typicalShowSchedule, seven nights a week]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalShowSchedule Context triple: [Village Vanguard, typicalShowSchedule, seven nights a week]
-
A.
showSchedule
Indicates that an entity presents or displays a timetable or planned sequence of events for another entity.
-
B.
televisionShow
Indicates that one entity is a television show associated with, or featured in relation to, another entity.
-
C.
primaryBroadcastSchedule
Indicates the main or default schedule according to which a broadcast is planned or transmitted.
-
D.
usedForTelevisionBroadcastSchedules
Indicates that something is utilized to organize, present, or manage the timing and content of television broadcast schedules.
-
E.
typicalSchedule
chosen
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea39e73081908e8d14118f9d1e03 |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:22 p.m.