Triple
T988802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queen Victoria |
E21338
|
entity |
| Predicate | titleStart:Empress of India |
P17919
|
FINISHED |
| Object | 1876 |
—
|
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: 1876 | Statement: [Queen Victoria, titleStart:Empress of India, 1876]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleStart:Empress of India Context triple: [Queen Victoria, titleStart:Empress of India, 1876]
-
A.
emperorTitle
chosen
Indicates that one entity holds the title or rank of emperor in relation to another entity.
-
B.
endTimeAsCapitalOfBritishIndia
Indicates the point in time when a location ceased to serve as the capital of British India.
-
C.
monarchMother
Indicates that one entity is the mother of another entity who holds or held a monarchical position (such as king, queen, emperor, etc.).
-
D.
reignAsEmpressConsortBegan
Indicates the point in time when an individual began their tenure or role as an empress consort.
-
E.
regentOf
Indicates a relationship where one entity serves as the ruling authority or caretaker governing on behalf of another entity, typically during the latter’s minority, absence, or incapacity.
- 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_69a493c383dc8190a03257f22d4b4183 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4aa16f081909dcc7a7ce3fb1b64 |
completed | March 1, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69a4b2abccbc8190a83af432f89eacf5 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.