Triple
T24310506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Chelmsford |
E612657
|
entity |
| Predicate | spouseOfViceroyRole |
P125296
|
FINISHED |
| Object | supported ceremonial and social duties of the Viceroy |
—
|
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: supported ceremonial and social duties of the Viceroy | Statement: [Lady Chelmsford, spouseOfViceroyRole, supported ceremonial and social duties of the Viceroy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spouseOfViceroyRole Context triple: [Lady Chelmsford, spouseOfViceroyRole, supported ceremonial and social duties of the Viceroy]
-
A.
spouseOfHeadOfState
Indicates that one person is the spouse (married partner) of a head of state.
-
B.
spouseOfLeader
Indicates that one entity is the married partner (spouse) of another entity who holds a leadership position.
-
C.
spouseOfRole
Indicates that one role is the spouse (husband, wife, or equivalent marital partner) of another role.
-
D.
spouseServedMonarch
Indicates that the spouse of a person held a position of service or duty to a monarch.
-
E.
spouseDiplomaticRole
chosen
Indicates that one person is the spouse of another person who holds or held a diplomatic position or role.
- 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2922a6afc8190b02cc2d185d15a45 |
completed | April 29, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f1c45f45888190a9ccc225906c34bd |
completed | April 29, 2026, 8:42 a.m. |
Created at: April 18, 2026, 1:33 a.m.