Triple
T8105129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superclásico (Boca vs River) |
E189207
|
entity |
| Predicate | hasViolenceHistory |
P37550
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Superclásico (Boca vs River), hasViolenceHistory, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasViolenceHistory Context triple: [Superclásico (Boca vs River), hasViolenceHistory, yes]
-
A.
hasTypeOfViolence
Indicates that an entity involves, exhibits, or is characterized by a specific kind or category of violent behavior or action.
-
B.
usedViolenceAgainst
Indicates that one entity intentionally inflicted physical force or harm upon another entity.
-
C.
hasHistoryOf
chosen
Indicates that an entity has a documented prior occurrence or background of a specified condition, event, or state.
-
D.
hasTragicPast
Indicates that an entity has experienced a significantly sorrowful or traumatic history that influences its present state or characterization.
-
E.
hasPerpetratorBackground
Indicates that an action, event, or crime is associated with information describing the background or history of its perpetrator.
- 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_69ca82b9d5848190a24672775d5c5011 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb42c0ce6481909887be82c8019383 |
completed | March 31, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69cb04a2ed1c8190b73562321ad688bc |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:31 p.m.