Triple
T16072933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Declaration of Legal Principles Governing the Activities of States in the Exploration and Use of Outer Space |
E389908
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | non‑binding declaration |
C28159
|
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: non‑binding declaration Context triple: [Declaration of Legal Principles Governing the Activities of States in the Exploration and Use of Outer Space, instanceOf, non‑binding declaration]
-
A.
non-binding international agreement
chosen
A non-binding international agreement is a formal understanding between states or international actors that expresses shared intentions or guidelines without creating legally enforceable obligations under international law.
-
B.
declaration
A declaration is a statement in a program that introduces an identifier (such as a variable, function, or type) and specifies its properties without necessarily providing its full implementation.
-
C.
diplomatic declaration
A diplomatic declaration is a formal, often public statement issued by a state or group of states to articulate positions, intentions, or commitments in international relations.
-
D.
non-normative document
A non-normative document is a text that provides guidance, explanation, or examples without establishing mandatory rules, requirements, or standards.
-
E.
declaration of principles
A declaration of principles is a formal statement that outlines the fundamental values, beliefs, and guiding rules that shape the behavior, decisions, or goals of an individual, group, or organization.
- F. None of above.
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_69d86daf32ec8190a8c0466c8f49c3c0 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:57 a.m.