Triple
T37806359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casino Royale |
E942511
|
entity |
| Predicate | introducedMotto |
P198817
|
FINISHED |
| Object | Bond’s vodka martini preference shaken not stirred (early form) |
—
|
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: Bond’s vodka martini preference shaken not stirred (early form) | Statement: [Casino Royale, introducedMotto, Bond’s vodka martini preference shaken not stirred (early form)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedMotto Context triple: [Casino Royale, introducedMotto, Bond’s vodka martini preference shaken not stirred (early form)]
-
A.
usesMotto
Indicates that one entity adopts or employs a particular motto as its guiding phrase or slogan.
-
B.
mottoIncluded
Indicates that a motto is present as part of, or associated with, the referenced entity.
-
C.
mottoOriginalLanguage
Indicates the language in which a motto was originally formulated or expressed.
-
D.
formerMotto
Indicates that a motto was previously used by an entity but is no longer its current motto.
-
E.
mottoOriginal
Indicates that one entity is the original wording or form of another entity’s motto.
- F. None of above. chosen
Provenance (4 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_69f76ee8104c8190ab17133ccd8f86e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff0b6bc4a88190bf1d38c6ea26bcdc |
completed | May 9, 2026, 10:24 a.m. |
| PD | Predicate disambiguation | batch_69ff082a22f4819095ded971dbd8ea7b |
completed | May 9, 2026, 10:10 a.m. |
| PDg | Predicate description generation | batch_69ff0b6a541c8190a6fa847552f3491f |
completed | May 9, 2026, 10:24 a.m. |
Created at: May 3, 2026, 4:19 p.m.