Triple
T24733473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Court of Henry VIII |
E618350
|
entity |
| Predicate | queenConsort |
P123691
|
FINISHED |
| Object | Catherine Parr |
—
|
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: Catherine Parr | Statement: [Court of Henry VIII, queenConsort, Catherine Parr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: queenConsort Context triple: [Court of Henry VIII, queenConsort, Catherine Parr]
-
A.
producedQueenConsort
Indicates that one entity gave rise to or is the origin of another entity who became a queen consort.
-
B.
reignAsQueenConsort
Indicates that a person holds the position and performs the role of queen consort during the reign of a monarch.
-
C.
typeOfMonarchConsort
chosen
Indicates the specific kind or category of monarch’s spouse (consort) that an entity is, such as queen consort, prince consort, or empress consort.
-
D.
regentSpouse
Indicates that one person is the spouse of a regent, i.e., married to an individual who rules on behalf of a monarch or in place of the sovereign.
-
E.
reignAsQueenConsortFrom
Indicates the time period during which a person held the role of queen consort, starting from a specified date or event.
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 4:03 a.m.