Triple
T29227986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Underground bombing |
E740985
|
entity |
| Predicate | partOfPlotByCharacter |
P95262
|
FINISHED |
| Object | Raoul Silva |
—
|
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: Raoul Silva | Statement: [London Underground bombing, partOfPlotByCharacter, Raoul Silva]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfPlotByCharacter Context triple: [London Underground bombing, partOfPlotByCharacter, Raoul Silva]
-
A.
plotCharacter
chosen
Indicates a relationship where a character plays a role or participates in the narrative plot of a story or work.
-
B.
relatedCharacter
Indicates that one character has a specified relationship or association with another character.
-
C.
relationshipToCharacter
Indicates the specific type of personal, social, or narrative connection that one entity has to a given character.
-
D.
givenByCharacter
Indicates that something (such as an item, information, or assistance) is provided or handed over by a particular character.
-
E.
relatedCharacterContext
Indicates a contextual relationship between characters, such as roles, interactions, or situational connections that link them within a specific narrative or setting.
- 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_69f07cbb12bc81908c1971d9de9a8d2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fe831c97c88190b27ecf100e25c2a0 |
completed | May 9, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69fe7f1b92648190b14e56bcaee5d0ca |
completed | May 9, 2026, 12:26 a.m. |
Created at: April 28, 2026, 12:17 p.m.