Triple
T38298226
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ranulf de Glanvill |
E1032152
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 12th-century English judge |
C63311
|
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: 12th-century English judge Context triple: [Ranulf de Glanvill, instanceOf, 12th-century English judge]
-
A.
Justiciar of England
The Justiciar of England was the king’s chief minister and principal royal administrator in medieval England, acting as regent in the monarch’s absence and overseeing justice, finance, and governance.
-
B.
12th-century English politician
chosen
A 12th-century English politician is a medieval public figure involved in the governance, administration, or advisory councils of the English crown or local authorities during the 1100s in England.
-
C.
13th-century English noble
A 13th-century English noble is a high-ranking landowning aristocrat who wields military, judicial, and political power under the feudal monarchy, owing loyalty to the king while exercising authority over vassals and estates.
-
D.
13th-century English bishop
A 13th-century English bishop was a high-ranking cleric in medieval England responsible for overseeing a diocese’s spiritual life, administering church law and property, and often advising the king in both religious and political matters.
-
E.
13th-century English politician
A 13th-century English politician was a medieval figure involved in the governance of England, often serving in roles such as a member of Parliament, royal administrator, or local official under the monarchy.
- 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:30 p.m.