Triple
T21610619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irena Dubrovna |
E533294
|
entity |
| Predicate | finalSceneInvolves |
P128609
|
FINISHED |
| Object | panther cage at the zoo |
—
|
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: panther cage at the zoo | Statement: [Irena Dubrovna, finalSceneInvolves, panther cage at the zoo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalSceneInvolves Context triple: [Irena Dubrovna, finalSceneInvolves, panther cage at the zoo]
-
A.
finalSceneAction
Indicates the action or event that occurs in the concluding or final scene of a narrative or sequence.
-
B.
finalAct
Indicates that an action or event is the last or concluding act in a sequence or process.
-
C.
laterFinale
Indicates that one event, episode, or occurrence serves as a concluding part that happens after another referenced event or finale.
-
D.
appearsInEpilogueOf
Indicates that one entity is featured or present in the epilogue section of another entity (such as a story, book, film, or other narrative work).
-
E.
hasFinale
chosen
Indicates that one entity serves as the concluding or final part (such as an ending segment, episode, or event) of another 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_69e0c46411108190bba0d4176dffc9f3 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef17e88f7081909371bc0de2147609 |
completed | April 27, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:33 p.m.