Triple

T4975954
Position Surface form Disambiguated ID Type / Status
Subject Battle of Narva (1700) E111765 entity
Predicate location P40 FINISHED
Object Narva E218186 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: Narva | Statement: [Battle of Narva (1700), location, Narva]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Narva
Context triple: [Battle of Narva (1700), location, Narva]
  • A. Narva chosen
    Narva is a historic city in northeastern Estonia on the border with Russia, known for its strategic military importance and well-preserved fortress overlooking the Narva River.
  • B. Vasai
    Vasai is a historic coastal town in western India, near Mumbai, known for its strategic importance under Portuguese and later British rule and as the site of the 1802 Treaty of Bassein.
  • C. Jelgava
    Jelgava is a city in central Latvia known for its historic Jelgava Palace and role as a regional cultural and educational center.
  • D. Reval
    Reval is the historical German name for Tallinn, the capital city and major port of present-day Estonia on the Baltic Sea.
  • E. Vyborg
    Vyborg is a historic port city in northwestern Russia near the Finnish border, known for its medieval castle and long-contested status between Sweden, Finland, and Russia.
  • 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_69bd441a0eb481908050fa4273b19eae completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd7230086c81909c045614721bd89f completed March 20, 2026, 4:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69be8a01e548819087e3a6ae2cd581b9 completed March 21, 2026, 12:07 p.m.
Created at: March 20, 2026, 1:33 p.m.