Triple
T30299528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanchia of Provence |
E770617
|
entity |
| Predicate | spouseCoronationTitle |
P37580
|
FINISHED |
| Object | King of the Romans |
—
|
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: King of the Romans | Statement: [Sanchia of Provence, spouseCoronationTitle, King of the Romans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseCoronationTitle Context triple: [Sanchia of Provence, spouseCoronationTitle, King of the Romans]
-
A.
spouseCrowned
Indicates that one person’s spouse was formally crowned, typically as a monarch or consort.
-
B.
consortTitleAtCoronation
chosen
Indicates the formal title held by a royal consort specifically at the time of a coronation.
-
C.
hasSpouseTitle
Indicates that a person’s spouse holds a particular title or honorific designation.
-
D.
pairedInRoyalTitleWith
Indicates that two individuals are jointly named or associated together within the same royal title (e.g., as co-rulers, consorts, or title partners).
-
E.
spouseNameAfterEnnoblement
Indicates that the predicate specifies the spouse’s name as it is used after the spouse has been ennobled or granted a noble title.
- 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: April 29, 2026, 7:48 p.m.