Triple
T21526896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oleanna |
E531119
|
entity |
| Predicate | productionHistory |
P105024
|
FINISHED |
| Object | frequently revived in regional theatres |
—
|
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: frequently revived in regional theatres | Statement: [Oleanna, productionHistory, frequently revived in regional theatres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionHistory Context triple: [Oleanna, productionHistory, frequently revived in regional theatres]
-
A.
hasProductionHistory
chosen
Indicates that an entity is associated with a record or account of its past production activities, processes, or outputs.
-
B.
historicProduct
Indicates that a product is no longer current and is recognized as belonging to an earlier or past period in the product’s lifecycle.
-
C.
categoryHistory
Indicates a relationship where an entity’s past or previous category assignments are recorded or referenced over time.
-
D.
productionBy
Indicates that something is created, manufactured, or generated by a particular agent, organization, or process.
-
E.
operationalHistory
Indicates the record of how something has been used, functioned, or operated over time, including its past activities and events.
- 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_69e0c45d95a081908e7962ad215da746 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee88515874819085e251c0d297a587 |
completed | April 26, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:26 p.m.