Triple
T32998775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess of Ryazan |
E844303
|
entity |
| Predicate | hasTypeOfConsort |
P198497
|
FINISHED |
| Object | hereditary consort |
—
|
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: hereditary consort | Statement: [Princess of Ryazan, hasTypeOfConsort, hereditary consort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfConsort Context triple: [Princess of Ryazan, hasTypeOfConsort, hereditary consort]
-
A.
hasConsortRole
Indicates that an entity holds or is assigned the role or status of a consort in relation to another entity.
-
B.
possibleConsortOf
Indicates that one entity is a potential or likely romantic or marital partner of another, without asserting that the relationship is confirmed.
-
C.
hasConsortDeityForm
Indicates that an entity has a consort specifically in their deity or divine form.
-
D.
linkedToConsort
Indicates a relationship in which one entity is connected or associated to another as its consort (spouse or formal partner).
-
E.
hasConcubineType
Indicates that an entity has or is associated with a concubine of a specified type or classification.
- 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_69f3494d99988190b502c68926af2c4d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69feecf1bb248190ba30f0bb1d22ee08 |
completed | May 9, 2026, 8:14 a.m. |
| PD | Predicate disambiguation | batch_69feea5f27748190b223ee4e3ba5a678 |
completed | May 9, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69feecf102e08190b237c29e45beeca0 |
completed | May 9, 2026, 8:14 a.m. |
Created at: May 1, 2026, 1:22 a.m.