Triple

T20244213
Position Surface form Disambiguated ID Type / Status
Subject Battle of Doiran (1917) E498378 entity
Predicate near P350 FINISHED
Object Doiran Lake
Doiran Lake is a transboundary lake on the border between North Macedonia and Greece, known as a strategic site of World War I battles between Allied and Bulgarian forces.
E1929869 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: Doiran Lake | Statement: [Battle of Doiran (1917), near, Doiran Lake]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Doiran Lake
Triple: [Battle of Doiran (1917), near, Doiran Lake]
Generated description
Doiran Lake is a transboundary lake on the border between North Macedonia and Greece, known as a strategic site of World War I battles between Allied and Bulgarian forces.

Provenance (5 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_69da6274c58c81909c646eabed6f4f30 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e67170aa248190922fc845d2265ae3 completed April 20, 2026, 6:33 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2898afbcac819090a462e0ddb1dc56 completed June 9, 2026, 10:50 p.m.
NEDg Description generation batch_6a289987c9988190a355050ae3113a08 completed June 9, 2026, 10:53 p.m.
NED2 Entity disambiguation (via description) batch_6a289d68dafc8190a4624b6bc4f54b9c completed June 9, 2026, 11:10 p.m.
Created at: April 11, 2026, 11:40 p.m.