Triple

T8681077
Position Surface form Disambiguated ID Type / Status
Subject Nassau-Beilstein line E206038 entity
Predicate hasTerritory P285 FINISHED
Object Nassau-Beilstein E41235 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: Nassau-Beilstein | Statement: [Nassau-Beilstein line, hasTerritory, Nassau-Beilstein]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nassau-Beilstein
Context triple: [Nassau-Beilstein line, hasTerritory, Nassau-Beilstein]
  • A. Nassau-Beilstein
    Nassau-Beilstein was a small German county and cadet branch territory of the House of Nassau within the Holy Roman Empire.
  • B. County of Nassau-Beilstein chosen
    The County of Nassau-Beilstein was a small territorial lordship within the Holy Roman Empire, ruled by a cadet branch of the House of Nassau.
  • C. Nassau-Siegen
    Nassau-Siegen was a German county in the Holy Roman Empire centered on the town of Siegen and ruled by a branch of the House of Nassau.
  • D. Nassau-Weilburg
    Nassau-Weilburg was a historical German county and later principality within the Holy Roman Empire, ruled by a branch of the House of Nassau.
  • E. Stolberg
    Stolberg is a historic German town in the Harz region, known for its well-preserved medieval architecture and role in early Reformation-era history.
  • 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_69ca835379688190aa06b9d98e684d58 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc4ae6d19c8190be003f7901c0468d completed March 31, 2026, 10:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69cf6ed1e0548190b02d43c5d7e65e08 completed April 3, 2026, 7:40 a.m.
Created at: March 30, 2026, 6:32 p.m.