Triple
T25509126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonario |
E639323
|
entity |
| Predicate | opposesTheme |
P133980
|
FINISHED |
| Object | corruption |
—
|
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: corruption | Statement: [Bonario, opposesTheme, corruption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposesTheme Context triple: [Bonario, opposesTheme, corruption]
-
A.
oppositionTheme
chosen
Indicates that one entity thematically represents or embodies opposition or conflict in relation to another entity.
-
B.
theoryOpposed
Indicates that one theory stands in opposition to, or conflicts with, another theory.
-
C.
opposesPhrase
Indicates that one entity expresses disagreement with, resistance to, or argument against the idea, statement, or position represented by the phrase.
-
D.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
E.
opposesIdentity
Indicates that one entity actively rejects, resists, or stands in opposition to the identity, self-conception, or defining characteristics of another 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 21, 2026, 2:48 p.m.