Triple
T33404642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gordy's Home |
E855404
|
entity |
| Predicate | incidentVictim |
P50002
|
FINISHED |
| Object | Ricky "Jupe" Park |
—
|
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: Ricky "Jupe" Park | Statement: [Gordy's Home, incidentVictim, Ricky "Jupe" Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: incidentVictim Context triple: [Gordy's Home, incidentVictim, Ricky "Jupe" Park]
-
A.
coVictim
Indicates that two or more entities are victims in the same harmful event or incident.
-
B.
incidentWith
Indicates that one entity is involved in, affected by, or associated with a particular incident or event together with another entity.
-
C.
incidentDescription
Indicates a textual explanation or narrative detailing the circumstances, events, and relevant facts associated with a particular incident.
-
D.
isVictimOf
chosen
Indicates that one entity suffers harm, loss, or wrongdoing as a result of another entity’s actions or events.
-
E.
victimStatus
Indicates the condition or state of a person who has been harmed or wronged as a result of an event, action, or offense.
- 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:36 a.m.