Triple
T19677597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryazan Oblast Duma |
E472494
|
entity |
| Predicate | createsLaw |
P57553
|
FINISHED |
| Object | laws of Ryazan Oblast |
—
|
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: laws of Ryazan Oblast | Statement: [Ryazan Oblast Duma, createsLaw, laws of Ryazan Oblast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createsLaw Context triple: [Ryazan Oblast Duma, createsLaw, laws of Ryazan Oblast]
-
A.
createsLawType
chosen
Indicates that an entity (such as a legislative body or authority) brings a specific type or category of law into existence.
-
B.
legalTool
Indicates a relationship where something functions as a legal instrument, mechanism, or means used to achieve or regulate a legal purpose or outcome.
-
C.
legalReformer
Indicates that an entity works to change, improve, or modernize laws or legal systems.
-
D.
legalCodeFocus
Indicates that something is specifically concerned with, centered on, or primarily addressing a particular legal code or body of law.
-
E.
draftingAdviser
Indicates that one entity serves as an adviser responsible for drafting or preparing documents, plans, or texts for 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e641bceef881909c5b655af709c8c6 |
completed | April 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69e514eb37b8819091502cc954f70eba |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:45 p.m.