Triple
T20041676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippsburg fortress |
E497435
|
entity |
| Predicate | controlledBy |
P1715
|
FINISHED |
| Object | Baden |
—
|
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: Baden | Statement: [Philippsburg fortress, controlledBy, Baden]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Baden Context triple: [Philippsburg fortress, controlledBy, Baden]
-
A.
Baden
Baden is a historic spa town in present-day Switzerland known for hosting the 1714 Treaty of Baden that helped conclude the War of the Spanish Succession.
-
B.
Baden
chosen
Baden was a historical state in southwestern Germany that existed as a grand duchy before being incorporated into the German Empire.
-
C.
Baden
Baden is a district or locality within the German town of Achim, situated in the state of Lower Saxony.
-
D.
Baden-Rodemachern
Baden-Rodemachern was a small German margraviate and noble residence associated with a cadet branch of the House of Baden in the early modern period.
-
E.
Baden-Durlach
Baden-Durlach was a historical Protestant margraviate in southwestern Germany that played a notable role in the religious and political conflicts of the Holy Roman Empire.
- 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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e662eb9a6081909d06dc1d457b4d5a |
completed | April 20, 2026, 5:31 p.m. |
Created at: April 11, 2026, 3:37 p.m.