Triple
T10520076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Duchess of Russia |
E248141
|
entity |
| Predicate | titleInHierarchy |
P35573
|
FINISHED |
| Object | below Empress of Russia |
—
|
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: below Empress of Russia | Statement: [Grand Duchess of Russia, titleInHierarchy, below Empress of Russia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleInHierarchy Context triple: [Grand Duchess of Russia, titleInHierarchy, below Empress of Russia]
-
A.
titleHierarchy
chosen
Indicates a hierarchical relationship between titles, where one title is ranked above or below another in an ordered structure.
-
B.
titles
Indicates that one entity holds a formal title, designation, or name associated with another entity.
-
C.
titleThrough
Indicates a relationship where one entity holds or is identified by a specific title by means of, or via the mediation of, another entity or context.
-
D.
title
Indicates that one entity serves as the formal name or designation of another entity.
-
E.
higherTitleOf
Indicates that one entity holds a job or position title that is hierarchically superior to the title held by another entity.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509de0b3081909bec337aa8ff193e |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:28 p.m.