Triple

T25894370
Position Surface form Disambiguated ID Type / Status
Subject Škurda River E652425 entity
Predicate near P350 FINISHED
Object Kotor Fortress
Kotor Fortress is a historic hilltop fortification overlooking the Bay of Kotor in Montenegro, renowned for its medieval walls and panoramic views of the old town and surrounding landscape.
E1705510 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: Kotor Fortress | Statement: [Škurda River, near, Kotor Fortress]
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: Kotor Fortress
Triple: [Škurda River, near, Kotor Fortress]
Generated description
Kotor Fortress is a historic hilltop fortification overlooking the Bay of Kotor in Montenegro, renowned for its medieval walls and panoramic views of the old town and surrounding landscape.

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_69e7ab3c6cc081908de59bfcc28ec19d completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f60382d4648190819e373a0880b74c completed May 2, 2026, 2 p.m.
NED1 Entity disambiguation (via context triple) batch_6a11076a0bf88190be6fef3c1c7abc5a completed May 23, 2026, 1:48 a.m.
NEDg Description generation batch_6a110b39a4148190be9232f46524444b completed May 23, 2026, 2:04 a.m.
NED2 Entity disambiguation (via description) batch_6a110b67bb9481909db5ab42fe96d9fa completed May 23, 2026, 2:05 a.m.
Created at: April 22, 2026, 8:22 a.m.