Triple
T36460450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philibert II, Duke of Savoy |
E898273
|
entity |
| Predicate | firstMarriageYear |
P98119
|
FINISHED |
| Object | 1496 |
—
|
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: 1496 | Statement: [Philibert II, Duke of Savoy, firstMarriageYear, 1496]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstMarriageYear Context triple: [Philibert II, Duke of Savoy, firstMarriageYear, 1496]
-
A.
marriedInYear
chosen
Indicates that two entities are married to each other in a specific calendar year.
-
B.
marriedOn
Indicates that a marriage event took place on a specific date for the related entities.
-
C.
marriageStartTime
Indicates the date and time at which a marriage between two entities officially begins.
-
D.
marriageOfHeadEndYear
Indicates the year in which the head of a marriage (e.g., household or family unit) ceased to be married, marking the end of that marital relationship.
-
E.
marriageDate
Indicates the specific date on which two entities entered into a marital relationship.
- 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_69f76e57f08481908593bd0bc34581c8 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.