Triple
T21150034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Constitution of 1906 |
E521162
|
entity |
| Predicate | favoredSuffrageFor |
P94601
|
FINISHED |
| Object | nobility |
—
|
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: nobility | Statement: [Russian Constitution of 1906, favoredSuffrageFor, nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: favoredSuffrageFor Context triple: [Russian Constitution of 1906, favoredSuffrageFor, nobility]
-
A.
grantsSuffrageTo
chosen
Indicates that one party confers the legal right to vote upon another party.
-
B.
hasTypeOfSuffrage
Indicates that an entity possesses or is characterized by a particular kind or form of suffrage (voting right).
-
C.
suffrage
Indicates that an entity has the right or privilege to vote in political or organizational decision-making processes.
-
D.
hasUniversalSuffrage
Indicates that all adult citizens in a given jurisdiction have the legal right to vote in public elections, regardless of characteristics such as gender, race, or wealth.
-
E.
dissolvedInFavorOf
Indicates that one entity has been formally terminated, annulled, or discontinued in order to benefit, support, or be replaced by another entity.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72400911c8190978e88138a9bfaff |
completed | April 21, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:58 p.m.