Triple
T4638660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Her Majesty The Empress |
E101595
|
entity |
| Predicate | isConsortTitle |
P50009
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Her Majesty The Empress, isConsortTitle, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConsortTitle Context triple: [Her Majesty The Empress, isConsortTitle, true]
-
A.
titleHeldAsConsort
chosen
Indicates that an individual holds a title specifically by virtue of being the consort (spouse) of the primary titleholder, rather than as the principal officeholder themselves.
-
B.
consortTitleAtCoronation
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.
isIndividualTitle
Indicates that a given title refers to a single, specific individual rather than a group, organization, or collective entity.
-
E.
hasConsortCrowned
Indicates that an individual has a spouse or consort who has been formally crowned, typically in a royal or ceremonial context.
- 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_69bd43d3bc7c81908f81fcf380476b0f |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a64214481908a207e8070cc7a45 |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5233cb5081908807e2b150f0ca06 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:13 p.m.