Triple
T26244642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Royal |
E656407
|
entity |
| Predicate | Victoria, Princess RoyalFather |
P160400
|
FINISHED |
| Object | Queen Victoria |
—
|
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: Queen Victoria | Statement: [Princess Royal, Victoria, Princess RoyalFather, Queen Victoria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Victoria, Princess RoyalFather Context triple: [Princess Royal, Victoria, Princess RoyalFather, Queen Victoria]
-
A.
predecessorAsPrincessRoyal
Indicates that one entity previously held the title or position of Princess Royal immediately before the other entity.
-
B.
holderPrincessMayOfTeckSpouse
Indicates that the holder has Princess May of Teck as their spouse.
-
C.
heldByPrincessLouiseDaughterOfEdwardVII
Indicates that something is possessed, owned, or held by Princess Louise, the daughter of Edward VII.
-
D.
PrincessElizabethRole
Indicates that an entity holds or is assigned the role or title associated with Princess Elizabeth in a given context.
-
E.
dateBecamePrincessRoyal
Indicates the specific date on which an individual assumed the title or status of Princess Royal.
- 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_69ee5b4c59a881909d9ee4fd013fffd5 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60dc5cbc48190952960eeab21cc9f |
completed | May 2, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f600be0de88190989611e952b03117 |
completed | May 2, 2026, 1:48 p.m. |
Created at: April 26, 2026, 9:05 p.m.