Triple
T19555829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thankmar |
E489306
|
entity |
| Predicate | burialPlace |
P196
|
FINISHED |
| Object | Eresburg |
—
|
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: Eresburg | Statement: [Thankmar, burialPlace, Eresburg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eresburg Context triple: [Thankmar, burialPlace, Eresburg]
-
A.
Eresburg
chosen
Eresburg was an early medieval fortress in present-day Germany, historically significant as a strategic stronghold in Saxon and Frankish conflicts.
-
B.
Escheburg
Escheburg is a small municipality in the district of Herzogtum Lauenburg in Schleswig-Holstein, northern Germany.
-
C.
Ebernburg
Ebernburg is a historic castle in Rhineland-Palatinate, Germany, known as a stronghold of the early Reformation and the seat of knight Franz von Sickingen.
-
D.
Biburg
Biburg is a small municipality in the Lower Bavarian region of Germany, known for its rural character and historic monastery.
-
E.
Vienenburg
Vienenburg is a district of Goslar in Lower Saxony, Germany, known for its historic town center and proximity to the Harz Mountains.
- 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_69d8e8dc5d8c8190a6d7bd8864f43ca0 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63d335f888190abfc5ba974d3c65e |
completed | April 20, 2026, 2:50 p.m. |
Created at: April 10, 2026, 1:42 p.m.