Triple
T44300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 51 of the United Nations Charter |
E869
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | article of an international treaty |
C544
|
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: article of an international treaty Context triple: [Article 51 of the United Nations Charter, instanceOf, article of an international treaty]
-
A.
founding treaty
A founding treaty is a formal, binding international agreement that establishes, constitutes, and defines the core structures, powers, and purposes of an international organization or political union.
-
B.
collective defense agreement
A collective defense agreement is a formal pact among multiple states committing each to consider an attack on one member as an attack on all and to respond with coordinated defense measures.
-
C.
intergovernmental organization
An intergovernmental organization is a formal entity created by sovereign states through treaties or agreements to cooperate on common interests, coordinate policies, and address international issues.
-
D.
international organization
An international organization is an institutional entity formed by multiple countries or global actors to coordinate policies, manage shared interests, and address transnational issues through cooperative frameworks and agreements.
-
E.
Act of Congress
An Act of Congress is a formal law or statute enacted by the United States Congress and, typically upon receiving the President’s signature or a veto override, becomes legally binding federal legislation.
- 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_69a247a8f6c08190bac804906d62ed5a |
completed | Feb. 28, 2026, 1:40 a.m. |
Created at: Feb. 28, 2026, 1:46 a.m.