Triple
T16767401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marshal of the Army of God and Holy Church |
E407501
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval English office |
C24745
|
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: medieval English office Context triple: [Marshal of the Army of God and Holy Church, instanceOf, medieval English office]
-
A.
medieval public office
chosen
A medieval public office is an institutional role within the governance structures of the Middle Ages, endowed with specific legal authority, duties, and privileges to administer justice, manage resources, or represent sovereign power on behalf of a ruler or community.
-
B.
Commonwealth of England office
A Commonwealth of England office is an administrative or governmental position or institution that operated under the republican regime of England (1649–1660), responsible for executing the functions of state in the absence of a monarchy.
-
C.
medieval court
A medieval court is the political and social center surrounding a monarch or noble, where governance, justice, ceremony, and daily life of the ruling elite are conducted.
-
D.
medieval parliament
A medieval parliament is an assembly of nobles, clergy, and sometimes commoners convened by a monarch to advise on governance, consent to taxation, and address matters of law and policy.
-
E.
public office in England and Wales
A public office in England and Wales is a position conferred by the state or a public authority that carries ongoing duties to the public, is created or recognized by law, and involves the exercise of public functions or powers.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:21 a.m.