Triple
T26611504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Khotyn (1788) |
E667935
|
entity |
| Predicate | countryDefender |
P62905
|
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: [Siege of Khotyn (1788), countryDefender, Ottoman Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryDefender Context triple: [Siege of Khotyn (1788), countryDefender, Ottoman Empire]
-
A.
countryOfDefender
chosen
Indicates the country to which the defending party or entity in a conflict, dispute, or legal case belongs.
-
B.
countryOfDefensivePreparation
Indicates the country in which defensive measures, planning, or preparations for protection or security are carried out or organized.
-
C.
countryAttacker
Indicates that one country is the aggressor or initiator of an attack against another country.
-
D.
defender
Indicates a relationship where one entity protects, guards, or supports another entity against threats, attacks, or criticism.
-
E.
defenseForces
Indicates a relationship where one entity serves as the military or protective force responsible for defending 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_69ee9cfe16088190a3dddd68e3c7b1ea |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: April 27, 2026, 2:16 a.m.