Triple
T8138255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicano theater |
E190025
|
entity |
| Predicate | combinesStyle |
P50934
|
FINISHED |
| Object | folkloric performance |
—
|
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: folkloric performance | Statement: [Chicano theater, combinesStyle, folkloric performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combinesStyle Context triple: [Chicano theater, combinesStyle, folkloric performance]
-
A.
styleCombination
chosen
Indicates a relationship where multiple styles are combined or coordinated to form a unified stylistic configuration or presentation.
-
B.
compositionStyle
Indicates the characteristic manner or approach in which something is composed, such as its structural, aesthetic, or stylistic conventions.
-
C.
uniformStyle
Indicates that the related entities share the same or a consistent style, pattern, or formatting.
-
D.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an entity.
-
E.
usedWithStyle
Indicates that something is employed or applied in conjunction with a particular style or stylistic manner.
- 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_69ca82bd9900819099477cdc2eb4244f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4402b35c81909363ffa9ce952ca4 |
completed | March 31, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69cb369c0d0481908762c488d7f77e74 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:35 p.m.