Triple
T28440114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teatro Chicano |
E715684
|
entity |
| Predicate | usesPerformanceMode |
P136488
|
FINISHED |
| Object | satire |
—
|
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: satire | Statement: [Teatro Chicano, usesPerformanceMode, satire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPerformanceMode Context triple: [Teatro Chicano, usesPerformanceMode, satire]
-
A.
intendedPerformanceMode
Indicates the manner or mode in which an action, process, or performance is meant or designed to be carried out.
-
B.
isHighPerformance
Indicates that an entity operates at a superior or above-standard level of efficiency, speed, or capability compared to typical expectations or benchmarks.
-
C.
typicalPerformanceMode
Indicates the usual or most common way in which an entity performs an action or operates.
-
D.
performanceUse
chosen
Indicates that something is used, employed, or utilized in the course of performing an action, task, or function.
-
E.
hasModernPerformance
Indicates that an entity includes, features, or is associated with a contemporary or updated performance or execution of something (such as a work, function, or capability).
- 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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 28, 2026, 1:45 a.m.