Triple
T37772753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | de Guise |
E941595
|
entity |
| Predicate | dynasticTitleAssociated |
P163921
|
FINISHED |
| Object | Duke of Guise |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Duke of Guise | Statement: [de Guise, dynasticTitleAssociated, Duke of Guise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynasticTitleAssociated Context triple: [de Guise, dynasticTitleAssociated, Duke of Guise]
-
A.
dynasticRole
Indicates the specific position, function, or status an entity holds within a dynasty or hereditary ruling line.
-
B.
dynasticStatus
Indicates the relationship between an entity and a ruling dynasty, such as membership in, association with, or status within that dynastic line.
-
C.
dynasticType
Indicates the specific kind or category of dynastic relationship or succession pattern that applies between ruling entities or lineages.
-
D.
associatedWithDynasty
Indicates that an entity has a historical, political, cultural, or familial connection to a specific dynasty.
-
E.
monarchicTitleHolderOf
chosen
Indicates that one entity holds a monarchic title associated with another entity (such as a realm, position, or office).
- F. None of above.
Provenance (3 batches)
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_69f76ee4431881908f87e8892a9f39f3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.