Triple
T16683447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Krasnoi |
E405397
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Krasny |
E762035
|
NE 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: Krasny | Statement: [Battle of Krasnoi, location, Krasny]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Krasny Context triple: [Battle of Krasnoi, location, Krasny]
-
A.
Krasny
chosen
Krasny is a town situated along the Sozh River, known for its regional administrative and cultural significance.
-
B.
Krasna
Krasna is a surname most notably associated with American screenwriter, playwright, and film producer Norman Krasna.
-
C.
Kraslava
Kraslava is a small town in southeastern Latvia known for its historic architecture and scenic location near the borders with Belarus and Lithuania.
-
D.
Krasnokokshaysk
Krasnokokshaysk is the former name of the city now known as Yoshkar-Ola, the capital of the Mari El Republic in Russia.
-
E.
Krasnov
Krasnov is a Russian surname borne by various notable figures in military, political, and cultural history.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37d70d3f8819087d1bd700c94a83f |
completed | April 18, 2026, 12:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a008a422f8c8190873fd7089df8fbd4 |
completed | May 10, 2026, 1:38 p.m. |
Created at: April 10, 2026, 5:19 a.m.