Triple
T34041504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neumark administration |
E872958
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical administrative body |
C1003
|
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: historical administrative body Context triple: [Neumark administration, instanceOf, historical administrative body]
-
A.
former administrative territorial entity
A former administrative territorial entity is a geographic area that once functioned as an official unit of government or administration but has since been dissolved, merged, or reorganized and no longer holds that status.
-
B.
public administration body
A public administration body is an organization within the public sector responsible for implementing laws, delivering public services, and managing governmental policies and resources on behalf of the state and its citizens.
-
C.
former political institution
chosen
A former political institution is an organization or governing body that once held official political authority or administrative power but has since been dissolved, replaced, or rendered inactive.
-
D.
civilian administrative body
A civilian administrative body is a non-military organization responsible for managing public affairs, implementing policies, and providing governmental services within a defined jurisdiction.
-
E.
ancient political entity
An ancient political entity is a historically situated, organized community or state that exercised authority, governance, and control over a defined territory and population in antiquity.
- 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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:51 a.m.