Triple

T10984066
Position Surface form Disambiguated ID Type / Status
Subject Reitdiep E259581 entity
Predicate hasSettlementOnBank P1010 FINISHED
Object Adorp E284502 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: Adorp | Statement: [Reitdiep, hasSettlementOnBank, Adorp]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Adorp
Context triple: [Reitdiep, hasSettlementOnBank, Adorp]
  • A. Adorp chosen
    Adorp is a small village in the municipality of Het Hogeland in the province of Groningen in the northern Netherlands.
  • B. Arlesheim
    Arlesheim is a municipality in the canton of Basel-Landschaft in northwestern Switzerland, known for its historic cathedral and picturesque setting near Basel.
  • C. Affoltern
    Affoltern is a district of Zurich, Switzerland, known as a largely residential area on the western side of the city.
  • D. Walchwil
    Walchwil is a picturesque Swiss municipality in the canton of Zug, known for its scenic location on the eastern shore of Lake Zug and views of the surrounding Alps.
  • E. Bremgarten
    Bremgarten is a historic Swiss town in the canton of Aargau, known for its well-preserved medieval old town and scenic riverside setting.
  • 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_69d6aa895f4c8190887a15460ef622f4 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d772ec55fc81909b2b15f2493dddc6 completed April 9, 2026, 9:35 a.m.
NED1 Entity disambiguation (via context triple) batch_69e3a954a1f481908c5653b8ddb09164 completed April 18, 2026, 3:55 p.m.
Created at: April 8, 2026, 9:24 p.m.