Triple
T26159670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cretan Revolt of 1878 |
E660071
|
entity |
| Predicate | hasRulingPowerOpposed |
P81732
|
FINISHED |
| Object | Ottoman Empire |
—
|
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: Ottoman Empire | Statement: [Cretan Revolt of 1878, hasRulingPowerOpposed, Ottoman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRulingPowerOpposed Context triple: [Cretan Revolt of 1878, hasRulingPowerOpposed, Ottoman Empire]
-
A.
hasOpposingFaction
Indicates that one faction stands in opposition or conflict to another faction.
-
B.
traditionallyOpposedRuler
Indicates that one entity has historically or customarily been in opposition to the rule or authority of another entity.
-
C.
hasBrokenAllianceWith
Indicates that a previously established alliance or partnership between two entities has been ended or violated by at least one of them.
-
D.
opponentInHistoricalConflict
chosen
Indicates that two entities stood on opposing sides in a specific historical conflict or war.
-
E.
opposingMonarch
Indicates that two monarchs are in opposition to each other, typically as rivals, enemies, or leaders of conflicting factions or states.
- 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 26, 2026, 8:29 p.m.