Triple
T20063986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IAU 2000 resolutions |
E499558
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | set of resolutions |
C3443
|
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: set of resolutions Context triple: [IAU 2000 resolutions, instanceOf, set of resolutions]
-
A.
party resolution
Party resolution is the process or mechanism by which conflicts, disputes, or uncertainties involving one or more parties in a system are identified, negotiated, and conclusively settled according to defined rules or criteria.
-
B.
joint resolution of the United States Congress
A joint resolution of the United States Congress is a legislative measure requiring approval by both the House and Senate and, in most cases, the President’s signature, often used for specific purposes such as constitutional amendments, continuing appropriations, or limited policy actions.
-
C.
resolution
chosen
Resolution is the process or outcome of resolving a problem, conflict, or ambiguity by reaching a clear, definitive, and often agreed-upon state or decision.
-
D.
church resolution
A church resolution is a formal written decision or statement adopted by a church body to express its position, intentions, or directives on specific issues of doctrine, governance, or practice.
-
E.
set of draft conclusions
A set of draft conclusions is a provisional collection of tentative, logically derived end statements that summarize current findings or reasoning, subject to further review and revision.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
Created at: April 11, 2026, 3:39 p.m.