Triple
T23514419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Case of the Perjured Parrot |
E572515
|
entity |
| Predicate | hasHumanVictim |
P142550
|
FINISHED |
| Object | murder victim |
—
|
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: murder victim | Statement: [The Case of the Perjured Parrot, hasHumanVictim, murder victim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHumanVictim Context triple: [The Case of the Perjured Parrot, hasHumanVictim, murder victim]
-
A.
hasVictims
Indicates that an entity has one or more individuals who have been harmed, injured, or adversely affected by it.
-
B.
hasTypeOfVictims
chosen
Indicates that an entity is associated with victims of a specified type or category.
-
C.
hasMainVictim
Indicates that an event, action, or harmful situation primarily targets or affects a specific victim as its main subject.
-
D.
hasVictimsCount
Indicates the number of victims associated with a particular event, action, or entity.
-
E.
isVictimOf
Indicates that one entity suffers harm, loss, or wrongdoing as a result of another entity’s actions or events.
- 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_69e245b5e4208190bac8a6509867e394 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1aa80d9048190ab735dddd301feb4 |
completed | April 29, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:08 p.m.