Triple
T33448558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landmeister |
E856571
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Teutonic Order position |
C33219
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Teutonic Order position Context triple: [Landmeister, instanceOf, Teutonic Order position]
-
A.
member of the Teutonic Order
A member of the Teutonic Order is a knight or cleric belonging to the medieval Catholic military order founded in the late 12th century, dedicated to crusading, missionary work, and the governance of conquered territories in Central and Eastern Europe.
-
B.
Grand Master of the Teutonic Order
chosen
The Grand Master of the Teutonic Order is the supreme head of the medieval Catholic military-religious order, overseeing its spiritual mission, military campaigns, territorial governance, and internal administration.
-
C.
Teutonic Order castle
A Teutonic Order castle is a fortified monastic stronghold built by the medieval Teutonic Knights, combining military, administrative, and religious functions within a characteristic brick or stone complex.
-
D.
former Teutonic Order castle
A former Teutonic Order castle is a medieval fortress originally built and used by the Teutonic Knights that has since lost its military or monastic function and been repurposed, abandoned, or preserved as a historical site.
-
E.
Grand Master of the Knights Hospitaller
The Grand Master of the Knights Hospitaller is the supreme leader and chief administrator of the Order, responsible for its spiritual direction, military command, and governance of its territories and members.
- F. None of above.
Provenance (1 batch)
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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:37 a.m.