Triple
T29434882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Bank |
E746541
|
entity |
| Predicate | openingNightEventIn |
P137639
|
FINISHED |
| Object | Ocean's Thirteen |
—
|
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: Ocean's Thirteen | Statement: [The Bank, openingNightEventIn, Ocean's Thirteen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingNightEventIn Context triple: [The Bank, openingNightEventIn, Ocean's Thirteen]
-
A.
hasOpeningNightEvent
chosen
Indicates that an entity is associated with a specific event marking the official opening night of a performance, exhibition, or similar occasion.
-
B.
openingPerformance
Indicates the performance or event that serves as the first or inaugural showing in a series, season, or run.
-
C.
openingTo
Indicates that one entity serves as an entrance, access point, or passage leading into or toward another entity.
-
D.
openedForEvent
Indicates that a venue or location is made accessible and operational specifically for a particular event.
-
E.
openingWorkOf
Indicates that one work serves as the first or introductory piece in relation to another work, such as the opening item in a sequence or collection.
- 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_69f0a7a180e48190ae775e40047dbcb5 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 28, 2026, 3:15 p.m.