Triple
T5816273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Küçük Kaynarca |
E128993
|
entity |
| Predicate | marked |
P67122
|
FINISHED |
| Object | major decline in Ottoman power |
—
|
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: major decline in Ottoman power | Statement: [Treaty of Küçük Kaynarca, marked, major decline in Ottoman power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marked Context triple: [Treaty of Küçük Kaynarca, marked, major decline in Ottoman power]
-
A.
marks
Indicates that one entity makes a visible or symbolic sign on, or designates, another entity for identification, emphasis, or distinction.
-
B.
marksOn
Indicates that one entity bears visible signs, traces, or imprints that have been made or left by another entity.
-
C.
marque
Indicates that one entity is the brand or make associated with another entity, such as a product, vehicle, or manufactured item.
-
D.
markType
Indicates the specific category or kind of mark associated with or applied to an entity.
-
E.
usedMark
Indicates that one entity has employed or applied a particular mark, symbol, or indicator in some context or action.
- 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_69c0084869e881908d7859492183ca7b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0333fdd7081908d829265caa2ac11 |
completed | March 22, 2026, 6:21 p.m. |
| PDg | Predicate description generation | batch_69c0400dbec08190b2ef73689b2c0c31 |
completed | March 22, 2026, 7:16 p.m. |
Created at: March 22, 2026, 3:53 p.m.