Triple
T16732085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anhalt Railway |
E406615
|
entity |
| Predicate | historicalRegion |
P915
|
FINISHED |
| Object | Anhalt |
E286774
|
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: Anhalt | Statement: [Anhalt Railway, historicalRegion, Anhalt]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Anhalt Context triple: [Anhalt Railway, historicalRegion, Anhalt]
-
A.
Anhalt
chosen
Anhalt is a historical region in central Germany that once formed a duchy and later a state, now largely part of the federal state of Saxony-Anhalt.
-
B.
Sachse
Sachse is a suburban city in the Dallas–Fort Worth metropolitan area of northeastern Texas.
-
C.
Brannenburg
Brannenburg is a Bavarian municipality in southern Germany, known for its scenic Alpine setting and outdoor recreation opportunities.
-
D.
Anhalt region
The Anhalt region is a historical area in central Germany that served as the core territory of various Anhalt principalities and duchies within the Holy Roman Empire and later German states.
-
E.
North Hesse
North Hesse is a region in the northern part of the German state of Hesse, centered around the city of Kassel and known for its forests, hills, and cultural heritage.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c362bb88190921fab43d76c3ee8 |
completed | April 18, 2026, 2:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a009d4a94688190aabe56c34e8cc2c3 |
completed | May 10, 2026, 2:59 p.m. |
Created at: April 10, 2026, 5:20 a.m.