Triple
T16291259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sobornoye Ulozheniye |
E395526
|
entity |
| Predicate | effectOnSocialStructure |
P4312
|
FINISHED |
| Object | strengthened the landed gentry |
—
|
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: strengthened the landed gentry | Statement: [Sobornoye Ulozheniye, effectOnSocialStructure, strengthened the landed gentry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnSocialStructure Context triple: [Sobornoye Ulozheniye, effectOnSocialStructure, strengthened the landed gentry]
-
A.
socialImpact
chosen
Indicates the extent to which an action, entity, or relationship affects society or communities, whether positively or negatively.
-
B.
effectOnOthers
Indicates the impact or influence that one entity’s actions, presence, or state has on other entities.
-
C.
effectOnUser
Indicates how an action, event, or condition influences or impacts a user.
-
D.
impactOnFamily
Indicates the effect or influence that something has on a family’s situation, dynamics, or well-being.
-
E.
effectOnMembers
Indicates the impact or influence that something has on the members of a group or organization.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2491821d0819086cffdd7551ba85a |
completed | April 17, 2026, 2:52 p.m. |
| PD | Predicate disambiguation | batch_69e219f68d308190b71c1601303f0628 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:05 a.m.