Triple
T32088944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlotte de La Marck |
E819528
|
entity |
| Predicate | titleHeldAsHeiress |
P197524
|
FINISHED |
| Object | heiress of Sedan |
—
|
LITERAL FINISHED |
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: heiress of Sedan | Statement: [Charlotte de La Marck, titleHeldAsHeiress, heiress of Sedan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHeldAsHeiress Context triple: [Charlotte de La Marck, titleHeldAsHeiress, heiress of Sedan]
-
A.
titleHeldAs
Indicates that an entity holds or possesses a specific title in a particular capacity or role.
-
B.
titleHolderHeirStatus
Indicates the relationship between a title holder and their designated heir, specifying the heir’s status or standing in the line of succession to that title.
-
C.
titleHeldTo
Indicates that one entity holds or possesses a specific title in relation to another entity or context.
-
D.
titleHeldThrough
Indicates that an entity holds or possesses a title by means of, or via the intermediary of, another entity or mechanism.
-
E.
titleHeldByFamily
Indicates that a particular title, rank, or honor is held collectively or traditionally by a specific family or family line.
- F. None of above. chosen
Provenance (4 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_69f349004b2481908ce2e50af0d579a8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe991bca608190b524e419642f4243 |
completed | May 9, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69fe979fc1c4819091fc48d63ea12063 |
completed | May 9, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69fe991abc6c81908edbb98d61c9ca73 |
completed | May 9, 2026, 2:16 a.m. |
Created at: May 1, 2026, 12:25 a.m.