Triple

T21046724
Position Surface form Disambiguated ID Type / Status
Subject Emanuel Sperner E518468 entity
Predicate placeOfBirth P1 FINISHED
Object Lauban NE NERFINISHED

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: Lauban | Statement: [Emanuel Sperner, placeOfBirth, Lauban]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lauban
Context triple: [Emanuel Sperner, placeOfBirth, Lauban]
  • A. Lauban chosen
    Lauban is the former German name for the town now known as Lubań, located in southwestern Poland near the Czech and German borders.
  • B. Talbach
    Talbach is a small stream in Switzerland that serves as a tributary of the Ergolz River in the Basel-Landschaft region.
  • C. Balchoth
    The Balchoth are a warlike Easterling people in J.R.R. Tolkien’s Middle-earth legendarium, known for serving Sauron and invading Gondor from the eastern lands.
  • D. Gollan
    Gollan is a surname of likely Scottish or British origin associated with individuals such as the communist leader John Gollan.
  • E. Lahab
    Lahab is a short Meccan chapter of the Qur’an that condemns Abu Lahab and his wife for their opposition to the Prophet Muhammad.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b50438e08190917e2538bb8bc034 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e6fcf4d26481908b639996500a8319 completed April 21, 2026, 4:28 a.m.
Created at: April 16, 2026, 2:34 p.m.