Triple
T23863368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchess of Parma (consort) |
E592509
|
entity |
| Predicate | titleHolderMarriageDate |
P198
|
FINISHED |
| Object | 1964-04-29 |
—
|
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: 1964-04-29 | Statement: [Duchess of Parma (consort), titleHolderMarriageDate, 1964-04-29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderMarriageDate Context triple: [Duchess of Parma (consort), titleHolderMarriageDate, 1964-04-29]
-
A.
marriageDate
chosen
Indicates the specific date on which two entities entered into a marital relationship.
-
B.
marriageStartTime
Indicates the date and time at which a marriage between two entities officially begins.
-
C.
titleHolderBirthDate
Indicates the date on which the person holding a particular title or position was born.
-
D.
marriageDateApproximate
Indicates that the recorded date of a marriage is not exact but an estimated or approximate value.
-
E.
marriedOn
Indicates that a marriage event took place on a specific date for the related entities.
- 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_69e25d22eb488190914b193aff952e83 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1cae16df4819081a8b3a395e45118 |
completed | April 29, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f1614a65a88190bde1efb368a151e4 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:13 p.m.