Triple
T36646313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prithvi Theatres |
E904726
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian theatre company |
C66064
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Indian theatre company Context triple: [Prithvi Theatres, instanceOf, Indian theatre company]
-
A.
Indian stage play
An Indian stage play is a live theatrical performance that blends dialogue, music, dance, and culturally rooted storytelling, often drawing from mythology, history, or social themes.
-
B.
French theatre company
A French theatre company is an organization based in France that produces, stages, and promotes live theatrical performances, often drawing on French dramatic traditions and contemporary works.
-
C.
English theatre company
An English theatre company is an organization based in England that produces, stages, and promotes live theatrical performances, often employing actors, directors, designers, and technical staff to present plays and related dramatic works to the public.
-
D.
independent theatre company
An independent theatre company is a self-governed performing arts organization that produces and presents theatrical works outside major institutional or commercial systems, typically prioritizing artistic autonomy and experimental or community-focused projects.
-
E.
regional theater company
A regional theater company is a professional performing arts organization that produces and presents live theatrical productions for a specific geographic area, often featuring local talent and serving as a cultural hub for its community.
- F. None of above. chosen
Provenance (1 batch)
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_69f76e6d3a3c81909db73eda9e0516bd |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:11 p.m.