Triple
T3968047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Winnipeg Fringe Theatre Festival |
E92262
|
entity |
| Predicate | typicalProgram |
P2192
|
FINISHED |
| Object | theatre 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: theatre performances | Statement: [Winnipeg Fringe Theatre Festival, typicalProgram, theatre performances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalProgram Context triple: [Winnipeg Fringe Theatre Festival, typicalProgram, theatre performances]
-
A.
notableProgramType
Indicates that the subject is recognized for or associated with a particular type or category of program.
-
B.
programType
chosen
Indicates the category or kind of program to which an entity belongs or with which it is associated.
-
C.
typicalProgramElement
Indicates that one program element is a representative or characteristic example of another program element or category of elements.
-
D.
famousProgram
Indicates that a program is widely recognized or well-known, typically for its impact, quality, or popularity.
-
E.
televisionShow
Indicates that one entity is a television show associated with, or featured in relation to, another 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_69aed96624188190ac8c45bb57ab72b5 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaca33e4819091957c7915857a42 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8f252b081909749d40440d372b2 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:32 p.m.