Triple
T21554768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Putnam County Playhouse |
E531860
|
entity |
| Predicate | typicalCastComposition |
P27858
|
FINISHED |
| Object | local amateur actors |
—
|
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: local amateur actors | Statement: [Putnam County Playhouse, typicalCastComposition, local amateur actors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCastComposition Context triple: [Putnam County Playhouse, typicalCastComposition, local amateur actors]
-
A.
typicalCast
chosen
Indicates that the associated entities form the usual or characteristic cast of characters commonly appearing in a given work or type of work.
-
B.
typicalCasting
Indicates that one entity is the usual or standard casting choice for portraying another entity (such as a role, character, or type).
-
C.
originalCast
Indicates that the subject is a member of the initial group of performers or participants who first originated a role or production.
-
D.
famousEnsemble
Indicates that the subject is a well-known group of performers or artists collectively recognized for their work.
-
E.
filmCoStar
Indicates that two people appeared together as co-actors in the same film.
- 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eed2de1c248190b303a4a55b022374 |
completed | April 27, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:29 p.m.