Triple
T29373327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blount family |
E744916
|
entity |
| Predicate | hasRoyalMistress |
P86632
|
FINISHED |
| Object | Elizabeth Blount |
—
|
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: Elizabeth Blount | Statement: [Blount family, hasRoyalMistress, Elizabeth Blount]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoyalMistress Context triple: [Blount family, hasRoyalMistress, Elizabeth Blount]
-
A.
royalMistressOf
chosen
Indicates that one person is the (typically unofficial) romantic or sexual partner of a royal figure, such as a king or prince.
-
B.
hasRoyalHouse
Indicates that an entity is associated with or belongs to a particular royal house or dynasty.
-
C.
hasRoyalConnection
Indicates a relationship where an entity is linked or associated in some notable way to royalty, a royal family, or a royal institution.
-
D.
hasRoyalCircle
Indicates that an entity belongs to, is part of, or is associated with a royal or monarch’s inner circle or court.
-
E.
hasRoyalStatus
Indicates that an entity possesses a recognized royal rank, title, or status within a monarchy or royal system.
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 28, 2026, 2:29 p.m.