Triple
T10245857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austin Powers |
E240210
|
entity |
| Predicate | basedOn |
P98
|
FINISHED |
| Object | James Bond |
E18670
|
NE 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 | Statement: [Austin Powers, basedOn, James Bond]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: James Bond Context triple: [Austin Powers, basedOn, James Bond]
-
A.
James Bond
chosen
James Bond is a fictional British secret agent, code-named 007, known for his espionage missions, suave demeanor, and presence in a long-running series of novels and films.
-
B.
Guy Fleming
Guy Fleming was a prominent American naturalist and conservationist known for his key role in preserving the Torrey Pines area in California.
-
C.
Jack Bond
Jack Bond is a British film and television director known for his work on music videos and collaborations with prominent artists.
-
D.
JC Bond
JC Bond is a film editor known for working on the movie "Big Eyes."
-
E.
Q (James Bond)
Q is the fictional head of Q Branch in the James Bond series, known for equipping 007 with advanced gadgets and technology.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d22cfe1c8190afae178e11a59b8b |
completed | April 7, 2026, 9:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d6f7a597188190880200d13784f18f |
completed | April 9, 2026, 12:49 a.m. |
Created at: April 6, 2026, 11:26 a.m.