Triple

T14754939
Position Surface form Disambiguated ID Type / Status
Subject 1. Bezirk E346706 entity
Predicate hasLandmark P105 FINISHED
Object Graben E392108 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: Graben | Statement: [1. Bezirk, hasLandmark, Graben]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Graben
Context triple: [1. Bezirk, hasLandmark, Graben]
  • A. Graben chosen
    Graben is a famous and historic pedestrian street in the center of Vienna, Austria, known for its upscale shops, cafes, and notable Baroque monuments.
  • B. Graben
    Graben is a municipality in the Augsburg district of Bavaria, Germany, known for its location in the Swabian region near the city of Augsburg.
  • C. Malita Graben
    Malita Graben is a structural depression and hydrocarbon-bearing sub-basin within the offshore Bonaparte Basin of northern Australia.
  • D. Calder Graben
    Calder Graben is a structural depression within Western Australia’s Bonaparte Basin, known as a hydrocarbon-bearing sub-basin formed by extensional tectonics.
  • E. Aareschlucht
    Aareschlucht is a dramatic limestone gorge in the Bernese Oberland of Switzerland, carved by the Aare River and known for its narrow walkways and towering rock walls.
  • 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_69d822e8896c819091169882f9b20486 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69dec7d59df08190a86da5048358bd6e completed April 14, 2026, 11:03 p.m.
NED1 Entity disambiguation (via context triple) batch_69fdfb9e1b8481909abea3daabe91302 completed May 8, 2026, 3:05 p.m.
Created at: April 10, 2026, 1:30 a.m.