Triple
T26681086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ann Bond |
E672612
|
entity |
| Predicate | sharesSurnameWithFictionalCharacter |
P184837
|
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: [Ann Bond, sharesSurnameWithFictionalCharacter, James Bond]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesSurnameWithFictionalCharacter Context triple: [Ann Bond, sharesSurnameWithFictionalCharacter, James Bond]
-
A.
namedAfterFictionalCharacter
Indicates that one entity has been given its name in honor of, or derived from, a fictional character.
-
B.
isGivenNameOfFictionalCharacter
Indicates that a given name is the personal name borne by a fictional character.
-
C.
hasFamilyNameInFiction
Indicates that a fictional character is associated with a particular family name within a work of fiction.
-
D.
usedAsFictionalCharacterSurname
Indicates that a surname is employed as the last name of a fictional character in a narrative work.
-
E.
sharesSurnameWithMany
Indicates that an entity has the same surname as a large number of other entities.
- F. None of above. chosen
Provenance (5 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_69eecda13424819092b17942c4edf722 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f7b628b17c8190aa058c1a51852a27 |
completed | May 3, 2026, 8:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a11ec48bccc8190a73373e3bdb27029 |
completed | May 23, 2026, 6:04 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b5cadd308190a864245a21b08f9a |
completed | May 3, 2026, 8:53 p.m. |
Created at: April 27, 2026, 3:20 a.m.