Triple
T8297638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tracy Bond |
E194260
|
entity |
| Predicate | relationshipWithJamesBond |
P60256
|
FINISHED |
| Object | love interest |
—
|
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: love interest | Statement: [Tracy Bond, relationshipWithJamesBond, love interest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWithJamesBond Context triple: [Tracy Bond, relationshipWithJamesBond, love interest]
-
A.
associatedWithActorPlayingBond
Indicates that one entity has a relationship or connection with an actor who has played the character James Bond.
-
B.
typicalInteractionWithJamesBond
Indicates the characteristic or commonly occurring way in which an entity interacts or engages with James Bond.
-
C.
successorAsJamesBond
Indicates that one entity took over the role of portraying James Bond from another entity.
-
D.
notableInteractionStyleWithJamesBond
Indicates a characteristic way in which an entity typically interacts or engages with James Bond.
-
E.
romanticOutcomeWithJamesBond
chosen
Indicates that there is a romantic relationship or romantic outcome involving James Bond and another entity.
- F. None of above.
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_69ca82e50ebc81909aa7b260c76bd757 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7dfa040c8190ab801b3910e39142 |
completed | March 31, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69cb70b5b5348190b296e0ecec95de60 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:53 p.m.