Triple
T33979529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Velikaya knyazhna |
E871236
|
entity |
| Predicate | usedForDescendantsOf |
P191602
|
FINISHED |
| Object | Russian emperor |
—
|
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: Russian emperor | Statement: [Velikaya knyazhna, usedForDescendantsOf, Russian emperor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForDescendantsOf Context triple: [Velikaya knyazhna, usedForDescendantsOf, Russian emperor]
-
A.
usedForChildrenOf
Indicates that something is intended to be used by or for the benefit of the children of a specified entity.
-
B.
usedAsParentFor
Indicates that one entity functions as the parent or container for another entity within a hierarchical or structural relationship.
-
C.
usedByPredecessorOf
Indicates that something is used by an entity that is the predecessor of another entity in a sequence or hierarchy.
-
D.
functionOfDescendants
Indicates that one entity serves as a function or role that is determined by, derived from, or dependent on its descendants.
-
E.
associatedWithDescendants
Indicates that an entity has a relationship or connection specifically involving the descendants of another entity.
- 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_69f3499da0188190ab1a4ff06fb06a2a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
| PDg | Predicate description generation | batch_69fce28a74508190aab36551094e8226 |
completed | May 7, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:50 a.m.