Triple
T31755515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Ratatouille (restaurant in the film’s ending) |
E810546
|
entity |
| Predicate | openedAfterEvent |
P22818
|
FINISHED |
| Object | closure of Gusteau’s restaurant |
—
|
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: closure of Gusteau’s restaurant | Statement: [La Ratatouille (restaurant in the film’s ending), openedAfterEvent, closure of Gusteau’s restaurant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAfterEvent Context triple: [La Ratatouille (restaurant in the film’s ending), openedAfterEvent, closure of Gusteau’s restaurant]
-
A.
openedAfter
chosen
Indicates that one entity was opened at a later time than another entity.
-
B.
openedByEvent
Indicates that something is initiated, activated, or made accessible as a direct result of a specific event.
-
C.
openedForEvent
Indicates that a venue or location is made accessible and operational specifically for a particular event.
-
D.
openedDuring
Indicates that an entity began operating, became accessible, or was inaugurated within a specified time period or event.
-
E.
openedBefore
Indicates that one entity was opened at an earlier time than 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 30, 2026, 11:29 p.m.