Triple
T24440127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theatre of the Oppressed |
E616234
|
entity |
| Predicate | conceptualizesAudienceAs |
P72617
|
FINISHED |
| Object | co-creators |
—
|
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: co-creators | Statement: [Theatre of the Oppressed, conceptualizesAudienceAs, co-creators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conceptualizesAudienceAs Context triple: [Theatre of the Oppressed, conceptualizesAudienceAs, co-creators]
-
A.
relatesToAudience
Indicates a general relationship or relevance between something and a particular audience or group of recipients.
-
B.
typicalAudience
Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
-
C.
audienceComposition
Indicates the makeup or distribution of different groups or segments within an audience in relation to something.
-
D.
audienceRole
chosen
Indicates the role or function an entity has as part of an audience in relation to another entity or event.
-
E.
audienceOrientation
Indicates how something is directed, tailored, or positioned with respect to a particular audience or group of recipients.
- 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_69e2d7ec44b081909ccaf1f3bbec0641 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2978a5cac81909d2141b606714fd4 |
completed | April 29, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:17 a.m.