Triple
T34268529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron of Rosny |
E879240
|
entity |
| Predicate | notableHolderTitleEvolution |
—
|
GENERATED |
| Object | later Duke of Sully |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableHolderTitleEvolution Context triple: [Baron of Rosny, notableHolderTitleEvolution, later Duke of Sully]
-
A.
hasNotableTitleHolderWhoBecame
chosen
Indicates that an entity has a notable title holder who later attained or transitioned into another specified role, status, or position.
-
B.
titleHolderNotably
Indicates that an entity holds a particular title in a way that is especially notable, distinguished, or worthy of specific mention.
-
C.
historicalTitleChange
Indicates that an entity’s official title has changed at some point in history, linking the old title to the new one.
-
D.
notableTitleHeld
Indicates that an entity has held a distinguished or noteworthy title, rank, or official position.
-
E.
titleHolderServedAs
Indicates that the entity holding a particular title also performed the role or function associated with that title.
- 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_69f349b4f5fc819094b441d18e95e5f1 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:56 a.m.