Triple
T35154155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Whipping Man |
E1015071
|
entity |
| Predicate | hasBeenProducedIn |
P3992
|
FINISHED |
| Object | regional theatres in the United States |
—
|
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: regional theatres in the United States | Statement: [The Whipping Man, hasBeenProducedIn, regional theatres in the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenProducedIn Context triple: [The Whipping Man, hasBeenProducedIn, regional theatres in the United States]
-
A.
isProducedFrom
Indicates that something is created, generated, or derived from a specified source or input.
-
B.
isProducedIn
chosen
Indicates that something is created, manufactured, or generated within a particular place, context, or process.
-
C.
hasProduction
Indicates that an entity is associated with, or responsible for, the creation or manufacture of another entity or product.
-
D.
producedAs
Indicates that one entity is created, generated, or brought into existence as a result or output of another entity or process.
-
E.
producedOn
Indicates that something was created, manufactured, or brought into existence at a specific date or time.
- 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_69f76ddb3a708190b521ba2970b17178 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:02 p.m.