Triple
T15985942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Proprietor of Maryland |
E387695
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | hereditary noble office |
C29084
|
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: hereditary noble office Context triple: [Lord Proprietor of Maryland, instanceOf, hereditary noble office]
-
A.
Polish noble office
A Polish noble office is a formal position or title within the historical governance and social hierarchy of the Polish–Lithuanian Commonwealth, held by members of the nobility (szlachta) and associated with specific administrative, judicial, or ceremonial duties.
-
B.
princely office
A princely office is an institutional role or position held by a prince or princely figure, encompassing the authority, duties, and ceremonial functions associated with governing or representing a principality or royal domain.
-
C.
system of hereditary titles
A system of hereditary titles is a structured hierarchy of ranks and honors that are legally or socially passed down through family lines, typically from one generation to the next.
-
D.
Hungarian noble title
A Hungarian noble title is a hereditary or granted rank within the historical social hierarchy of the Kingdom of Hungary, denoting status, privileges, and obligations among the nobility.
-
E.
dynastic office
chosen
A dynastic office is a formal position of authority or responsibility that is inherited within a family line, typically passing from one generation to the next.
- 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_69d86daa562c81908aacc179c0fe8fb5 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:54 a.m.