Triple
T31120718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shannon (Despicable Me 2) |
E793213
|
entity |
| Predicate | settingOfKeyScene |
P171710
|
FINISHED |
| Object | 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: restaurant | Statement: [Shannon (Despicable Me 2), settingOfKeyScene, restaurant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfKeyScene Context triple: [Shannon (Despicable Me 2), settingOfKeyScene, restaurant]
-
A.
isSettingOfScene
chosen
Indicates that a particular location, time, or environment serves as the backdrop or context in which a scene takes place.
-
B.
timeOfKeyScene
Indicates the specific time at which a key or pivotal scene occurs within a larger sequence or event.
-
C.
associatedWithKeyScene
Indicates that something is linked or connected to a specific key scene, typically as a relevant element, feature, or reference.
-
D.
centralScene
Indicates that one scene functions as the main or focal scene within a larger narrative, sequence, or composition.
-
E.
settingOfKeyEvent
Indicates that a particular location or context is where a key or pivotal event takes place.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 29, 2026, 9:04 p.m.