Triple
T20157687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Octopussy and The Living Daylights |
E491615
|
entity |
| Predicate | hasFranchiseProtagonistTrait |
P138882
|
FINISHED |
| Object | sophisticated |
—
|
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: sophisticated | Statement: [Octopussy and The Living Daylights, hasFranchiseProtagonistTrait, sophisticated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFranchiseProtagonistTrait Context triple: [Octopussy and The Living Daylights, hasFranchiseProtagonistTrait, sophisticated]
-
A.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
B.
franchiseCharacter
Indicates a relationship where a character belongs to, appears in, or is part of a particular media franchise.
-
C.
hasChildProtagonist
Indicates that the work features a child as its main or central character.
-
D.
hasSpiritProtagonist
Indicates that the primary or central character in a narrative is a spirit or non-corporeal being.
-
E.
franchiseOriginCharacter
Indicates that a character is the original or primary character from which a franchise or its derivative works originate.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667e18a0c8190a2cc2b305da28047 |
completed | April 20, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69e54cfd924881909b55f3e4d3e7e070 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc2bc3c819088c33cd263303433 |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:34 p.m.