Triple
T3208965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William IV, Prince of Orange |
E67232
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prince of Orange |
C2394
|
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: prince of Orange Context triple: [William IV, Prince of Orange, instanceOf, prince of Orange]
-
A.
Prince of Orange
chosen
The Prince of Orange is a hereditary noble title historically associated with the sovereign rulers of the Principality of Orange and later with the heir apparent to the Dutch throne.
-
B.
King of Holland
The King of Holland is the hereditary head of state of the Netherlands, representing national unity, performing constitutional and ceremonial duties, and serving as a symbolic figure domestically and internationally.
-
C.
Dutch regent
A Dutch regent was a member of the wealthy urban patrician elite who governed cities and provinces in the Dutch Republic, often holding multiple civic offices and exerting significant political and economic influence.
-
D.
Princess of Orange
The Princess of Orange is a noble title traditionally held by the heir apparent or consort within the Dutch royal family, associated with the historical Principality of Orange.
-
E.
Duke of Brunswick-Lüneburg
The Duke of Brunswick-Lüneburg was a title held by various princes of the Holy Roman Empire who ruled over the duchy of Brunswick-Lüneburg in what is now northern Germany, often dividing and reuniting its territories among different dynastic lines.
- 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_69ad858ac36c81909962589cd277d6e2 |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:07 p.m.