Triple
T10697391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of the RSFSR (1937) |
E252179
|
entity |
| Predicate | declaresRight |
P19204
|
FINISHED |
| Object | right to work |
—
|
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: right to work | Statement: [Constitution of the RSFSR (1937), declaresRight, right to work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: declaresRight Context triple: [Constitution of the RSFSR (1937), declaresRight, right to work]
-
A.
establishesRight
chosen
Indicates that one entity creates or confers a legal or formal entitlement or privilege upon another entity.
-
B.
impliedRight
Indicates that one party holds a right or entitlement that is not explicitly stated but is inferred from context, agreements, or established norms.
-
C.
declared
Indicates that an entity formally announces, states, or proclaims something, often with official or authoritative intent.
-
D.
declaredTo
Indicates that one entity formally made a statement, announcement, or assertion to another specific entity.
-
E.
claimedRight
Indicates that an entity asserts or demands a right or entitlement in relation to another entity or resource.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd89390c8190969ab2b4a79d5818 |
completed | April 9, 2026, 1:14 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8cc0788190b4c02a772e4b58b3 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:12 p.m.