Triple

T32581490
Position Surface form Disambiguated ID Type / Status
Subject Qabala District E832800 entity
Predicate hasTouristAttraction P530 FINISHED
Object Nohur Lake
Nohur Lake is a scenic mountain lake in Azerbaijan known for its tranquil setting, forested surroundings, and popularity as a leisure and ecotourism destination.
E2287978 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: Nohur Lake | Statement: [Qabala District, hasTouristAttraction, Nohur 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: Nohur Lake
Triple: [Qabala District, hasTouristAttraction, Nohur Lake]
Generated description
Nohur Lake is a scenic mountain lake in Azerbaijan known for its tranquil setting, forested surroundings, and popularity as a leisure and ecotourism destination.

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_69f349289adc81909f4374a58ec35a39 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c669d6408190bc26dbf21f59e237 completed May 3, 2026, 3:52 a.m.
NED1 Entity disambiguation (via context triple) batch_6a5a5247607c8190a16d7833f29a92bd completed July 17, 2026, 4:03 p.m.
NEDg Description generation batch_6a5a52f482948190b8fe9d5074361763 completed July 17, 2026, 4:06 p.m.
NED2 Entity disambiguation (via description) batch_6a5a54647fb08190b4a87a342ce5f401 completed July 17, 2026, 4:12 p.m.
Created at: May 1, 2026, 1:04 a.m.