Triple
T31303678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martin Whitly |
E798276
|
entity |
| Predicate | roleInProdigalSon |
P140406
|
FINISHED |
| Object | serial killer |
—
|
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: serial killer | Statement: [Martin Whitly, roleInProdigalSon, serial killer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInProdigalSon Context triple: [Martin Whitly, roleInProdigalSon, serial killer]
-
A.
sonRole
Indicates that one entity holds the role or relationship of a son with respect to another entity.
-
B.
roleInTheProphecy
Indicates that an entity holds a specific function, status, or significance within the context of a particular prophecy.
-
C.
roleOfCharacter
chosen
Indicates that one entity serves as the narrative or functional role played by a character within a story, scenario, or context.
-
D.
roleInGuitarHero
Indicates the specific function or part an entity has within the context of the Guitar Hero game (e.g., player role, character role, or gameplay position).
-
E.
roleInTheMangler
Indicates that an entity has a specific role or involvement in the work titled "The Mangler."
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffac35ac5481908b6bdfd5bbe8c76e |
completed | May 9, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69ffabbfd2548190964c851496bbbaee |
completed | May 9, 2026, 9:48 p.m. |
Created at: April 29, 2026, 9:14 p.m.