Triple
T1165833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchess of York |
E24596
|
entity |
| Predicate | titleBecomes |
P25426
|
FINISHED |
| Object | Queen consort when husband accedes to the throne |
—
|
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: Queen consort when husband accedes to the throne | Statement: [Duchess of York, titleBecomes, Queen consort when husband accedes to the throne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleBecomes Context triple: [Duchess of York, titleBecomes, Queen consort when husband accedes to the throne]
-
A.
title
Indicates that one entity serves as the formal name or designation of another entity.
-
B.
titleIIFocus
Indicates that the primary focus or subject of a Title II–related provision, requirement, or classification is the referenced entity.
-
C.
titles
Indicates that one entity holds a formal title, designation, or name associated with another entity.
-
D.
retitledAs
Indicates that an entity has been given a new title or name, replacing or supplementing its original one.
-
E.
titleType
Indicates the specific category or kind of title associated with an entity (e.g., whether it is a main title, alternative title, working title, etc.).
- F. None of above. chosen
Provenance (4 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bccc62a88190882d8801908015a4 |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb548c1481909092626c572d8782 |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bc8ae87c81908ca5d94f63ad0e80 |
completed | March 1, 2026, 10:24 p.m. |
Created at: March 1, 2026, 7:45 p.m.