Triple
T36196219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Effect (Off-Broadway production) |
E1047131
|
entity |
| Predicate | isAProductionOf |
P46755
|
FINISHED |
| Object | The Effect (play) |
—
|
NE NERFINISHED |
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: The Effect (play) | Statement: [The Effect (Off-Broadway production), isAProductionOf, The Effect (play)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAProductionOf Context triple: [The Effect (Off-Broadway production), isAProductionOf, The Effect (play)]
-
A.
isProducedFrom
Indicates that something is created, generated, or derived from a specified source or input.
-
B.
producedAs
Indicates that one entity is created, generated, or brought into existence as a result or output of another entity or process.
-
C.
isProducedIn
Indicates that something is created, manufactured, or generated within a particular place, context, or process.
-
D.
producedSaint
Indicates that an entity (such as a place, group, or lineage) has given rise to or brought forth a particular saint.
-
E.
associatedProduction
chosen
Indicates that there is a related or connected production (such as a work, performance, or manufacturing process) linked to the subject entity.
- 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_69f76e414bdc8190996f15a544220a3d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.