Triple
T220250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A/RES/217 A (III) |
E4196
|
entity |
| Predicate | article21Right |
P4517
|
FINISHED |
| Object | participation in government |
—
|
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: participation in government | Statement: [A/RES/217 A (III), article21Right, participation in government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: article21Right Context triple: [A/RES/217 A (III), article21Right, participation in government]
-
A.
article9Provision
Indicates a relationship where a specific legal or contractual element is identified as a provision contained within Article 9 of a larger document or agreement.
-
B.
articleType
Indicates the specific category or kind of article associated with an entity.
-
C.
keyArticle
Indicates that an article is a primary or central reference for understanding, supporting, or defining another entity or topic.
-
D.
concernsRight
chosen
Indicates that something is about or relates specifically to a legal or moral right held by an entity.
-
E.
Article5Meaning
Indicates that a legal or policy document specifies the meaning, scope, or implications of its Article 5 provision.
- 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25efd0df48190b8fef4c422a1265f |
completed | Feb. 28, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69a25b54d790819093b35bd1a6f00f92 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.