Triple
T27551286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Coast Repertory |
E695505
|
entity |
| Predicate | producesPerSeason |
P57387
|
FINISHED |
| Object | 10 to 12 plays |
—
|
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: 10 to 12 plays | Statement: [South Coast Repertory, producesPerSeason, 10 to 12 plays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: producesPerSeason Context triple: [South Coast Repertory, producesPerSeason, 10 to 12 plays]
-
A.
producedSeason
Indicates that one entity produced or was responsible for creating a particular season of another entity, such as a TV series or show.
-
B.
productionSeason
Indicates the time period or season during which something is produced or created.
-
C.
annualProductions
chosen
Indicates a relationship where a specified number or set of items is produced each year by an entity.
-
D.
numberOfSeriesPerSeason
Indicates the total count of series (or episodes/instalments) that occur within a single season of something.
-
E.
playsTwicePerSeason
Indicates that one entity participates in or performs the specified activity or event exactly two times during each season.
- 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_69ef5386c3e08190bfe33aa326e1f72b |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 27, 2026, 1:35 p.m.