Triple
T24278420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Bond Island |
E605473
|
entity |
| Predicate | filmLocationForCharacter |
P155640
|
FINISHED |
| Object | James Bond (Agent 007) |
—
|
NE NERFINISHED |
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 (Agent 007) | Statement: [James Bond Island, filmLocationForCharacter, James Bond (Agent 007)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filmLocationForCharacter Context triple: [James Bond Island, filmLocationForCharacter, James Bond (Agent 007)]
-
A.
filmLocationFor
Indicates a relationship where a specific place serves as the filming location for a particular film or production.
-
B.
workLocationOfFictionalCharacter
Indicates the place or organization where a fictional character is depicted as working within their narrative context.
-
C.
placementInFilm
Indicates the specific position or occurrence of something within the sequence or structure of a film.
-
D.
formerFilmingLocation
Indicates that a place was once used as a filming location for a work but is no longer used for that purpose.
-
E.
filmingLocationForAdaptation
Indicates the place where an adaptation (such as a film or TV version of a work) was shot or recorded.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f5032f48190a027e2d8b382ee79 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f27a753ca8819095706970d368f762 |
completed | April 29, 2026, 9:39 p.m. |
Created at: April 18, 2026, 12:07 a.m.