Triple
T18880103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Factory Theater |
E461802
|
entity |
| Predicate | hasProductionModel |
P61118
|
FINISHED |
| Object | ensemble-driven creation |
—
|
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: ensemble-driven creation | Statement: [The Factory Theater, hasProductionModel, ensemble-driven creation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProductionModel Context triple: [The Factory Theater, hasProductionModel, ensemble-driven creation]
-
A.
usesProductionModel
chosen
Indicates that one entity employs or relies on another entity as its primary or official production model in practice.
-
B.
hasProduction
Indicates that an entity is associated with, or responsible for, the creation or manufacture of another entity or product.
-
C.
producedModel
Indicates that one entity created, manufactured, or generated the other entity as a model or product.
-
D.
hasProductionBase
Indicates that one entity serves as the primary location or base where another entity’s production or manufacturing activities are carried out.
-
E.
modelProduced
Indicates that a particular model has generated or produced a specified output, result, or artifact.
- 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c3d133f08190a482e601c1866662 |
completed | April 20, 2026, 6:12 a.m. |
| PD | Predicate disambiguation | batch_69e48d22dde8819093b1d963bd673365 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.