Triple
T36227699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ana Lucia Cortez |
E891148
|
entity |
| Predicate | shootingPerpetrator |
P111316
|
FINISHED |
| Object | Jason McCormack |
—
|
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: Jason McCormack | Statement: [Ana Lucia Cortez, shootingPerpetrator, Jason McCormack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shootingPerpetrator Context triple: [Ana Lucia Cortez, shootingPerpetrator, Jason McCormack]
-
A.
perpetratorOfKilling
Indicates that an entity is the one who carried out or caused a particular killing.
-
B.
shooter
chosen
Indicates that one entity performs a shooting action directed at another entity.
-
C.
perpetratorType
Indicates the classification or category of the entity that carried out or is responsible for a harmful, illegal, or otherwise wrongful act.
-
D.
perpetratorInCase
Indicates that an entity is the person or group responsible for committing the offense or wrongdoing in a particular legal or investigative case.
-
E.
perpetratedBy
Indicates that an action, event, or wrongdoing was carried out or caused by a particular agent or entity.
- 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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b5a0d2a48190a32496970ed5f223 |
completed | May 3, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.