Triple
T25019673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Fat Guy Strangler |
E626536
|
entity |
| Predicate | notableVictimType |
P19083
|
FINISHED |
| Object | fat men |
—
|
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: fat men | Statement: [The Fat Guy Strangler, notableVictimType, fat men]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVictimType Context triple: [The Fat Guy Strangler, notableVictimType, fat men]
-
A.
notableVictim
Indicates that the subject is a person or entity who is notably recognized as a victim of the object (such as an event, crime, or harmful action).
-
B.
notableVictims
chosen
Indicates that the object is a person or group who is especially well-known or significant as a victim of the subject.
-
C.
notableVictimNationality
Indicates that the relationship specifies the nationality of a notable victim associated with an event, incident, or action.
-
D.
mainVictims
Indicates that the related entities are the primary or principal targets harmed or affected by an action, event, or perpetrator.
-
E.
victimOfExecutionBy
Indicates that one entity was executed as a result of an execution carried out by 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 18, 2026, 6:06 a.m.