Triple
T23617086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stompie Seipei affair |
E583203
|
entity |
| Predicate | victimAlias |
P153283
|
FINISHED |
| Object | Stompie |
—
|
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: Stompie | Statement: [Stompie Seipei affair, victimAlias, Stompie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: victimAlias Context triple: [Stompie Seipei affair, victimAlias, Stompie]
-
A.
victimRole
Indicates that one entity participates in an event or situation specifically in the role of the victim or harmed party.
-
B.
victimFullName
Indicates the complete personal name of the individual who is the victim in the described event or relationship.
-
C.
victimCharacter
Indicates that one entity is the victim or target of harm, wrongdoing, or an adverse action carried out by another entity.
-
D.
victimSide
Indicates that one entity is on, represents, or corresponds to the side of the victim in a conflict, incident, or harmful event.
-
E.
victimParty
Indicates that one party is the victim or harmed side in an event, action, or situation involving another party.
- 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_69e248fbcd9081908ba08913f9d30826 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b175b2208190a78e1d4aac191709 |
completed | April 29, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f138b8c9248190b059bc38a9a50958 |
completed | April 28, 2026, 10:46 p.m. |
Created at: April 17, 2026, 6:45 p.m.