Triple

T3608656
Position Surface form Disambiguated ID Type / Status
Subject court of Trier E76432 entity
Predicate locatedIn P40 FINISHED
Object Germania E78932 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: Germania | Statement: [court of Trier, locatedIn, Germania]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Germania
Context triple: [court of Trier, locatedIn, Germania]
  • A. Germania chosen
    Germania was the ancient Roman term for the vast region of central Europe inhabited by various Germanic tribes beyond the empire’s northeastern frontiers.
  • B. Teutônia
    Teutônia is a municipality in the Brazilian state of Rio Grande do Sul known for its strong German-Brazilian cultural heritage and traditions.
  • C. Saksa
    Saksa is a prominent mountain in Norway’s Sunnmøre Alps, known for its steep ascent and panoramic views over the Hjørundfjord.
  • D. Prussia
    Prussia was a historically powerful German state and kingdom that became a leading military and political force in Europe, ultimately playing a central role in the unification of Germany.
  • E. German Empire
    The German Empire was a unified German nation-state that existed from 1871 to 1918 under Prussian-dominated imperial rule, culminating in its defeat in World War I.
  • 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_69ad85da0ba481908b3b48c69efe2b98 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc22a3cf081908c20b6fb55be0db2 completed March 8, 2026, 6:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4e4d974f081909c98ddaf55aab8cc completed March 14, 2026, 4:32 a.m.
Created at: March 8, 2026, 3:22 p.m.