Triple
T15838562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Köroghlu |
E384042
|
entity |
| Predicate | opposesInLegend |
P119852
|
FINISHED |
| Object | unjust rulers |
—
|
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: unjust rulers | Statement: [Köroghlu, opposesInLegend, unjust rulers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposesInLegend Context triple: [Köroghlu, opposesInLegend, unjust rulers]
-
A.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
B.
opposesLabel
Indicates that one entity expresses disagreement with, resistance to, or active opposition against another entity or its position.
-
C.
isOppositionCounterpartOf
Indicates a relationship where one entity serves as the opposing or counterpart force, side, or position to another within a conflict, competition, or contrast.
-
D.
symbolicOpposition
Indicates a relationship where one entity stands in conceptual or representational contrast to another, typically as an opposing symbol, idea, or sign.
-
E.
designedToOppose
Indicates that one entity is intentionally created or configured to counteract, resist, or work against another entity or process.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e142e4fa24819086a1a226082ac2d3 |
completed | April 16, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69e007647f908190adb178c68c7bb7cf |
completed | April 15, 2026, 9:47 p.m. |
Created at: April 10, 2026, 4:49 a.m.