Triple
T17389253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elena Glinskaya |
E422771
|
entity |
| Predicate | consolidatedPowerAgainst |
P4392
|
FINISHED |
| Object | boyar families |
—
|
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: boyar families | Statement: [Elena Glinskaya, consolidatedPowerAgainst, boyar families]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consolidatedPowerAgainst Context triple: [Elena Glinskaya, consolidatedPowerAgainst, boyar families]
-
A.
combinesPowers
Indicates that two or more entities merge their abilities or strengths to produce a unified, often enhanced, effect.
-
B.
majorPowerUntil
Indicates that an entity functioned as a major power or dominant force up to, but not beyond, a specified time or event.
-
C.
opposingAlliance
Indicates that two entities belong to rival or mutually opposed alliances or factions.
-
D.
majorPowerIn
Indicates that an entity holds significant political, economic, or military influence within a specified domain, region, or context.
-
E.
exclusivePower
chosen
Indicates that one entity holds sole authority or control over another entity or a specific domain, excluding others from sharing that power.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a8c718c81909cb20749aaf12897 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.