Triple
T27389259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duchess of Oldenburg |
E691473
|
entity |
| Predicate | linkedToImperialFamily |
P109317
|
FINISHED |
| Object | Russian imperial family |
—
|
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: Russian imperial family | Statement: [Duchess of Oldenburg, linkedToImperialFamily, Russian imperial family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkedToImperialFamily Context triple: [Duchess of Oldenburg, linkedToImperialFamily, Russian imperial family]
-
A.
associatedWithImperialSuccession
Indicates a relationship where an entity is connected to, involved in, or relevant to the process or events of imperial succession.
-
B.
hasBranchOfImperialFamily
Indicates that an entity includes or is associated with a specific branch or lineage of an imperial family.
-
C.
hadMemberInImperialFamily
chosen
Indicates that an entity had at least one member belonging to an imperial family.
-
D.
rankWithinImperialFamily
Indicates the hierarchical position an individual holds within an imperial family relative to other family members.
-
E.
associatedWithDynasty
Indicates that an entity has a historical, political, cultural, or familial connection to a specific dynasty.
- 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_69ef520386788190bc92cfcd97ebb67a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 27, 2026, 12:25 p.m.