Triple
T12482687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jesus (bass) |
E298350
|
entity |
| Predicate | roleOpposedTo |
P43226
|
FINISHED |
| Object | Evangelist (tenor) |
—
|
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: Evangelist (tenor) | Statement: [Jesus (bass), roleOpposedTo, Evangelist (tenor)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOpposedTo Context triple: [Jesus (bass), roleOpposedTo, Evangelist (tenor)]
-
A.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
B.
isOppositionCounterpartOf
chosen
Indicates a relationship where one entity serves as the opposing or counterpart force, side, or position to another within a conflict, competition, or contrast.
-
C.
roleWhenInOpposition
Indicates the specific role or function an entity assumes when it is in a state of opposition to another entity or group.
-
D.
typeOfOpposition
Indicates a relationship where one entity stands in opposition or contrast to another, such as being a rival, adversary, or countering force.
-
E.
opposedByGroup
Indicates that an action, proposal, or entity is met with opposition or resistance from a particular group.
- 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_69d6ada377208190a36011199a4d8558 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e8a706c8190873623eab7db607d |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d41f3cc8190a3331fb9a895306f |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:56 p.m.