Triple
T4502456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | casino at Royale-les-Eaux |
E101252
|
entity |
| Predicate | settingForEvent |
P2808
|
FINISHED |
| Object | James Bond’s confrontation with Le Chiffre |
—
|
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: James Bond’s confrontation with Le Chiffre | Statement: [casino at Royale-les-Eaux, settingForEvent, James Bond’s confrontation with Le Chiffre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingForEvent Context triple: [casino at Royale-les-Eaux, settingForEvent, James Bond’s confrontation with Le Chiffre]
-
A.
setting
Indicates the place, time, or context in which an event, action, or interaction occurs.
-
B.
settingOfActivities
Indicates that a particular place or context serves as the environment in which certain activities occur or are carried out.
-
C.
setInEvent
chosen
Indicates that an entity is situated within, occurs during, or is contextually located in a particular event.
-
D.
eventUse
Indicates that an event involves the use or utilization of a particular entity (e.g., a resource, tool, or method) as part of its occurrence.
-
E.
audienceSetting
Indicates the context or environment in which an audience is situated or addressed.
- 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_69bd43d175248190894dc58b5b395c26 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd56fb2bec8190b74b6a49d9475514 |
completed | March 20, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69bd521671688190bc655d25fa77eba2 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1 p.m.