Triple
T22092965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carlos the Jackal in Carlos |
E545953
|
entity |
| Predicate | themeInvolves |
P25955
|
FINISHED |
| Object | political violence |
—
|
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: political violence | Statement: [Carlos the Jackal in Carlos, themeInvolves, political violence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: themeInvolves Context triple: [Carlos the Jackal in Carlos, themeInvolves, political violence]
-
A.
themeFor
chosen
Indicates that something serves as the central subject, topic, or focus for another thing (such as an event, work, or activity).
-
B.
followsInTheme
Indicates that one element continues or succeeds another while maintaining the same theme or thematic context.
-
C.
themeInvolvingCharacter
Indicates that a theme, motif, or abstract concept centrally involves or is significantly shaped by a particular character.
-
D.
theme
Indicates the entity that is the primary participant or content affected or characterized by an action, event, or state.
-
E.
themeInspiration
Indicates that one entity serves as the creative source or conceptual basis that inspires or shapes the theme expressed in 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_69e11e36d03c8190a83a1ba802b7231b |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f128e6b1d881909bf0f4a52199354c |
completed | April 28, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69e71b20ec50819096ac196c798f8e3c |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:29 p.m.