Triple

T10397282
Position Surface form Disambiguated ID Type / Status
Subject Albert of Cologne E245052 entity
Predicate placeOfBirth P1 FINISHED
Object Lauingen E386724 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: Lauingen | Statement: [Albert of Cologne, placeOfBirth, Lauingen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lauingen
Context triple: [Albert of Cologne, placeOfBirth, Lauingen]
  • A. Lauingen chosen
    Lauingen is a historic Bavarian town in southern Germany, best known as the birthplace of the medieval scholar and philosopher Albert the Great.
  • B. Herzogenaurach
    Herzogenaurach is a Bavarian town in Germany best known as the birthplace and headquarters of the global sportswear brands Adidas and Puma.
  • C. Gröbenzell
    Gröbenzell is a suburban town in Upper Bavaria, Germany, known for its residential character and proximity to Munich.
  • D. Pfeffenhausen
    Pfeffenhausen is a market town in Lower Bavaria, Germany, known for its rural character and location within the Landshut district.
  • E. Schwabmünchen
    Schwabmünchen is a small Bavarian town in southern Germany known for its historic center and location near the city of Augsburg.
  • 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_69d381b5116081908d85227bab6d3c0c completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4e9d0de448190b0bfd4d6c87d47fa completed April 7, 2026, 11:26 a.m.
NED1 Entity disambiguation (via context triple) batch_69f12f646ec88190ab4745c52798b599 completed April 28, 2026, 10:06 p.m.
Created at: April 6, 2026, 12:07 p.m.