Triple
T27214429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simon (The Walking Dead) |
E684097
|
entity |
| Predicate | ordersMassacreOf |
P141261
|
FINISHED |
| Object | Oceanside's male residents |
—
|
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: Oceanside's male residents | Statement: [Simon (The Walking Dead), ordersMassacreOf, Oceanside's male residents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ordersMassacreOf Context triple: [Simon (The Walking Dead), ordersMassacreOf, Oceanside's male residents]
-
A.
massacreAlsoKnownAs
Indicates that a particular massacre is known or referred to by an alternative name or names.
-
B.
massacreOccurredIn
Indicates that a massacre took place within the specified location or area.
-
C.
massacreOccurred
Indicates that a large-scale, deliberate killing of multiple individuals took place in a specific event or context.
-
D.
massacreOrderedBy
chosen
Indicates that a massacre was carried out under the command, authorization, or directive of a particular person or authority.
-
E.
commitsMassacreAt
Indicates that an entity carries out a large-scale, deliberate killing of many people at a specified location or event.
- 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 9:40 a.m.