Triple
T22948394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James "Rhodey" Rhodes |
E569936
|
entity |
| Predicate | roleRelativeToTonyStark |
P106280
|
FINISHED |
| Object | bodyguard and partner in combat |
—
|
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: bodyguard and partner in combat | Statement: [James "Rhodey" Rhodes, roleRelativeToTonyStark, bodyguard and partner in combat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleRelativeToTonyStark Context triple: [James "Rhodey" Rhodes, roleRelativeToTonyStark, bodyguard and partner in combat]
-
A.
roleInTonyStarkLife
chosen
Indicates the specific role or significance an entity has in Tony Stark's life.
-
B.
roleInAgeOfUltron
Indicates that an entity has a specific role or participation in the context of "Age of Ultron" (e.g., the film or storyline).
-
C.
roleInAvengers
Indicates that an entity has a specific role or membership status within the Avengers team.
-
D.
roleOnGalactica
Indicates the specific position, duty, or function an entity holds aboard the Battlestar Galactica.
-
E.
roleAccordingTo
Indicates that an entity holds a particular role or function as defined or interpreted by a specified source or perspective.
- 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_69e2459199d08190a8184ee2aa935842 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1819fbf8c8190ad80c93f1507aa73 |
completed | April 29, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:46 p.m.