Triple
T33897226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christy Brzonkala |
E868945
|
entity |
| Predicate | allegedAssaultLocation |
P184635
|
FINISHED |
| Object | Virginia Tech campus |
—
|
NE NERFINISHED |
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: Virginia Tech campus | Statement: [Christy Brzonkala, allegedAssaultLocation, Virginia Tech campus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allegedAssaultLocation Context triple: [Christy Brzonkala, allegedAssaultLocation, Virginia Tech campus]
-
A.
allegedShooterLocation
Indicates the place where a person is claimed or reported to have carried out a shooting.
-
B.
assaultedBy
Indicates that an entity has been attacked or subjected to violent physical aggression by another entity.
-
C.
attackedIn
Indicates that one entity carried out an attack in the location, context, or time frame specified by another entity or value.
-
D.
assassinationAttemptLocation
Indicates the place where an attempted assassination occurred or was intended to occur.
-
E.
assaultLedBy
Indicates that an assault was directed or coordinated by a particular person or group.
- F. None of above. chosen
Provenance (4 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_69f34997703c8190866b1d404bce531f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7b365288c8190bcb11fcfba028737 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2f2b9ac8190aa05b8a1aa18ec2d |
completed | May 3, 2026, 8:41 p.m. |
Created at: May 1, 2026, 1:48 a.m.