Triple
T24974182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchess of Albemarle |
E624971
|
entity |
| Predicate | spousalTitleOf |
P77742
|
FINISHED |
| Object | Duke of Albemarle |
—
|
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: Duke of Albemarle | Statement: [Duchess of Albemarle, spousalTitleOf, Duke of Albemarle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spousalTitleOf Context triple: [Duchess of Albemarle, spousalTitleOf, Duke of Albemarle]
-
A.
spouseNameWithTitle
Indicates that a person’s spouse is identified by name together with an associated honorific or title.
-
B.
isSpouseOfTitle
Indicates that one entity holds a spousal relationship specifically associated with a titled or honorific status of another entity.
-
C.
hasSpouseTitle
Indicates that a person’s spouse holds a particular title or honorific designation.
-
D.
titleFromSpouse
chosen
Indicates that an entity holds a title or honorific that is derived from or acquired through their spouse.
-
E.
spouseTitleOfSecondHusband
Indicates that the object is the formal title or designation held by a person’s second husband.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:01 a.m.