Triple

T6196092
Position Surface form Disambiguated ID Type / Status
Subject Ullern E138511 entity
Predicate locatedNear P294 FINISHED
Object Oslofjord E33322 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: Oslofjord | Statement: [Ullern, locatedNear, Oslofjord]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Oslofjord
Context triple: [Ullern, locatedNear, Oslofjord]
  • A. Oslofjord chosen
    Oslofjord is a large inlet in southeastern Norway known for its islands, coastal towns, and role as the maritime gateway to Oslo.
  • B. Drammensfjord
    Drammensfjord is a branch of the Oslofjord in southeastern Norway, known for its deep waters, surrounding industrial and urban areas, and role as an important maritime route.
  • C. Isfjorden
    Isfjorden is a major Arctic fjord on the west coast of Spitsbergen in the Svalbard archipelago, known for its dramatic glacial landscapes and as a key hub for human settlement and wildlife.
  • D. Storfjorden
    Storfjorden is a major fjord in western Norway known for its dramatic landscapes and proximity to the coastal town of Ålesund.
  • E. Osafjorden
    Osafjorden is a side fjord of Norway’s Hardangerfjord, known for its steep mountain scenery and tranquil, narrow waters.
  • 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_69c008ab9b3081908a11b2c744838435 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0624571508190bd273b4a051fbe41 completed March 22, 2026, 9:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69c640a2faf4819089bfbce9710ed22d completed March 27, 2026, 8:32 a.m.
Created at: March 22, 2026, 4:20 p.m.