Triple
T38504345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Shadow of Violence |
E921722
|
entity |
| Predicate | protagonistLoyaltyTo |
P47185
|
FINISHED |
| Object | crime family |
—
|
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: crime family | Statement: [The Shadow of Violence, protagonistLoyaltyTo, crime family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistLoyaltyTo Context triple: [The Shadow of Violence, protagonistLoyaltyTo, crime family]
-
A.
protagonistAllegiance
chosen
Indicates the group, cause, or side with which the main character is aligned or to which they show loyalty.
-
B.
isLoyalTo
Indicates that one entity consistently supports, respects, or remains faithful to another entity.
-
C.
allegianceSymbolizes
Indicates that one entity serves as a symbol or emblem representing another entity’s allegiance or loyalty.
-
D.
allegiance
Indicates a relationship where one entity is loyal, committed, or obligated in support or service to another entity.
-
E.
loyaltyConflict
Indicates a situation where an entity’s loyalties to different people, groups, or principles are in tension or opposition, creating a conflict in choosing whom or what to support.
- 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_69f76ea3c5448190aa7002fc1ba3f874 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.