Triple

T23384837
Position Surface form Disambiguated ID Type / Status
Subject Hjelmeland E593849 entity
Predicate hasCoastlineOn P212 FINISHED
Object Hjelmelandsfjorden
Hjelmelandsfjorden is a fjord in Rogaland county, Norway, known for its steep surrounding landscapes and role as a central waterway for the Hjelmeland area.
E2286793 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: Hjelmelandsfjorden | Statement: [Hjelmeland, hasCoastlineOn, Hjelmelandsfjorden]
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: Hjelmelandsfjorden
Triple: [Hjelmeland, hasCoastlineOn, Hjelmelandsfjorden]
Generated description
Hjelmelandsfjorden is a fjord in Rogaland county, Norway, known for its steep surrounding landscapes and role as a central waterway for the Hjelmeland area.

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_69e25d2754fc819085deea939bde60ab completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1a497661c8190b52fa27419594989 completed April 29, 2026, 6:26 a.m.
NED1 Entity disambiguation (via context triple) batch_6a472604b0648190aa53209d199d6f73 completed July 3, 2026, 3:01 a.m.
NEDg Description generation batch_6a472b689e3081909e50582f5c1d913c completed July 3, 2026, 3:24 a.m.
NED2 Entity disambiguation (via description) batch_6a472d3fba908190b05706e4d7b83df5 completed July 3, 2026, 3:32 a.m.
Created at: April 17, 2026, 5:35 p.m.