Triple
T21278118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Bishopric of Fulda |
E524444
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Fulda |
—
|
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: Fulda | Statement: [Prince-Bishopric of Fulda, capital, Fulda]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fulda Context triple: [Prince-Bishopric of Fulda, capital, Fulda]
-
A.
Fulda
Fulda is a major river in central Germany that flows through the state of Hesse and joins the Werra to form the Weser.
-
B.
Fulda
chosen
Fulda is a historic city in central Germany known for its Baroque architecture and former status as an important monastic and ecclesiastical center.
-
C.
Alsfeld
Alsfeld is a historic town in the German state of Hesse, renowned for its well-preserved medieval timber-framed architecture and picturesque old town.
-
D.
Merseburg
Merseburg is a historic town in the German state of Saxony-Anhalt, known for its medieval cathedral and role as an important cultural and administrative center on the River Saale.
-
E.
Hildesheim
Hildesheim is a historic city in northern Germany renowned for its medieval architecture and UNESCO-listed Romanesque churches.
- 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_69e0b516293c819089458ea2ec85f85e |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73658f598819098a1192abfa40a12 |
completed | April 21, 2026, 8:33 a.m. |
Created at: April 16, 2026, 4:02 p.m.