Triple
T23681081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ottoman garrison of Belgrade |
E585020
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Belgrade-based military formation |
C47948
|
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: Belgrade-based military formation Context triple: [Ottoman garrison of Belgrade, instanceOf, Belgrade-based military formation]
-
A.
municipality of Belgrade
A municipality of Belgrade is an administrative subdivision of the City of Belgrade that manages local governance, public services, and community affairs within its defined urban or suburban territory.
-
B.
Serbian organization
A Serbian organization is a structured group or entity based in Serbia that coordinates people and resources to pursue specific social, economic, cultural, political, or charitable objectives within the Serbian context.
-
C.
district of Serbia
A district of Serbia is an administrative territorial unit that groups multiple municipalities and cities for regional governance, coordination of state administration, and statistical purposes.
-
D.
entity of Bosnia and Herzegovina
An entity of Bosnia and Herzegovina is one of the two main political-administrative divisions of the country, each possessing its own government, constitution, and significant autonomy within the sovereign state.
-
E.
Serbian military commander
A Serbian military commander is a high-ranking officer responsible for planning, directing, and overseeing the operations, strategy, and personnel of Serbian armed forces in peace and wartime.
- F. None of above. chosen
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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:51 p.m.