Triple
T25198474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Invention of Morel |
E631064
|
entity |
| Predicate | subsequentProductionBy |
P82027
|
FINISHED |
| Object | Long Beach Opera |
—
|
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: Long Beach Opera | Statement: [The Invention of Morel, subsequentProductionBy, Long Beach Opera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentProductionBy Context triple: [The Invention of Morel, subsequentProductionBy, Long Beach Opera]
-
A.
followedByInProductionOrder
Indicates that one process, step, or item directly succeeds another in a defined production sequence or workflow order.
-
B.
laterProduction
chosen
Indicates that one production event or version occurs after another in time.
-
C.
firstProductionAfter
Indicates that one production event occurs immediately after another in a defined sequence or timeline.
-
D.
laterProducedBy
Indicates that something is produced or created by an entity at a later time than some referenced or implied production event.
-
E.
precededByInProductionOrder
Indicates that one production step or item occurs earlier than and directly before another in the defined production sequence.
- 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_69e75a8b86c4819089eda22c843b739f |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f474b409808190b41f2edafc801130 |
completed | May 1, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 12:50 p.m.