Triple
T14983490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dmitry Donskoy |
E373640
|
entity |
| Predicate | honorificOrigin |
P116939
|
FINISHED |
| Object | victory near the Don River at Kulikovo Field |
—
|
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: victory near the Don River at Kulikovo Field | Statement: [Dmitry Donskoy, honorificOrigin, victory near the Don River at Kulikovo Field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorificOrigin Context triple: [Dmitry Donskoy, honorificOrigin, victory near the Don River at Kulikovo Field]
-
A.
honorificSense
Indicates that one entity refers to another using an honorific or respectful linguistic form.
-
B.
honorificUsage
Indicates that one entity refers to or addresses another using an honorific title or respectful linguistic form.
-
C.
honorificIndicates
Indicates that one entity uses an honorific title or respectful form of address to refer to or address another entity.
-
D.
honorificForRegion
Indicates that a particular honorific title or form of address is specifically used for, or associated with, a given geographic region.
-
E.
honorificNature
Indicates that the relationship involves the use or assignment of an honorific title or respectful form of address between entities.
- 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6fe42a081909308f788fdf024d5 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:52 a.m.