Triple
T2625092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West End theatres |
E59097
|
entity |
| Predicate | typicalPerformanceSchedule |
P6833
|
FINISHED |
| Object | evening performances |
—
|
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: evening performances | Statement: [West End theatres, typicalPerformanceSchedule, evening performances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPerformanceSchedule Context triple: [West End theatres, typicalPerformanceSchedule, evening performances]
-
A.
typicalSchedule
Indicates the usual or standard timing and sequence of activities or events associated with an entity.
-
B.
typicalTimes
chosen
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
-
C.
typicalStartPeriod
Indicates the usual or standard time period during which something begins or is initiated.
-
D.
typicalPerformanceMode
Indicates the usual or most common way in which an entity performs an action or operates.
-
E.
typicalDates
Indicates the usual or standard dates during which something typically occurs, is valid, or is scheduled.
- 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_69ab4ac558388190962492cd2e1b0ce6 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abdaca581881908fe8d3d820f839b7 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd80f48888190afdf7e3e042157d0 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.