Triple
T33114328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiffany |
E847417
|
entity |
| Predicate | killsHumans |
P74108
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tiffany, killsHumans, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: killsHumans Context triple: [Tiffany, killsHumans, true]
-
A.
killsOrIsKilledBy
Indicates that one entity causes the death of the other or is itself killed by that entity, capturing a mutual or directional lethal relationship between them.
-
B.
typeOfKilling
Indicates a specific manner, method, or category of killing that characterizes how the killing was carried out.
-
C.
killedManyVictims
Indicates that an entity has killed a large number of distinct victims.
-
D.
perpetratorOfKilling
chosen
Indicates that an entity is the one who carried out or caused a particular killing.
-
E.
casualtiesHuman
Indicates a relationship where a human entity suffers harm, injury, or death as a result of an event, action, or situation.
- 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6ecf6488190970a6852742adb14 |
completed | May 3, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69f6d27224708190b31a541cebe0ff77 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:27 a.m.