Triple
T31528592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | general obligations |
E804411
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | obligation |
C57542
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: obligation Context triple: [general obligations, instanceOf, obligation]
-
A.
administrative obligation
An administrative obligation is a duty imposed on individuals or organizations to complete specific formal procedures, filings, or compliance tasks required by governing authorities or institutional rules.
-
B.
federal obligation
A federal obligation is a legally binding duty or commitment imposed or recognized by the national government, typically involving the payment of money, provision of services, or compliance with regulatory requirements.
-
C.
international legal obligation
An international legal obligation is a binding duty imposed on states or other international actors by treaties, customary international law, or general legal principles, requiring specific conduct or results in their relations with one another.
-
D.
dependency
A dependency is a relationship in which one entity relies on another to function correctly, be fulfilled, or achieve a particular outcome.
-
E.
obligation arising from UN Security Council resolutions
An obligation arising from UN Security Council resolutions is a binding duty imposed on states or other international actors by a resolution adopted under the Council’s authority, particularly under Chapter VII of the UN Charter, requiring specific actions or omissions to maintain or restore international peace and security.
- F. None of above. chosen
Provenance (1 batch)
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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 10 p.m.