Triple
T28088809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corrientes 1300–1500 theater district |
E709898
|
entity |
| Predicate | mainPerformingArtsGenres |
P21380
|
FINISHED |
| Object | theater |
—
|
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: theater | Statement: [Corrientes 1300–1500 theater district, mainPerformingArtsGenres, theater]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainPerformingArtsGenres Context triple: [Corrientes 1300–1500 theater district, mainPerformingArtsGenres, theater]
-
A.
performingArtsDomain
Indicates that the subject operates within, is related to, or is characterized by the field of performing arts.
-
B.
inArtGenre
Indicates that an artwork or artistic work belongs to, is classified under, or is created in a particular art genre.
-
C.
genreSpecialty
chosen
Indicates that an entity specializes in or is particularly associated with a specific genre.
-
D.
musicGenreCategory
Indicates that one entity is a broader music genre category under which the other music genre is classified.
-
E.
operaGenre
Indicates that an opera belongs to or is categorized under a particular musical or dramatic genre.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 8:57 p.m.