Triple
T4650996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Single Resolution Board |
E102294
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | resolution authority |
C14004
|
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: resolution authority Context triple: [Single Resolution Board, instanceOf, resolution authority]
-
A.
resolution
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.
-
B.
registration authority
A registration authority is an entity responsible for verifying the identity and eligibility of subjects and approving or managing their registration within a specified system or domain.
-
C.
identifier resolution system
An identifier resolution system is a mechanism that maps unique identifiers to their corresponding resources or entities, enabling consistent lookup, retrieval, and management across distributed or heterogeneous environments.
-
D.
administrative authority
chosen
An administrative authority is an organization or body empowered by law or policy to implement, manage, and enforce rules, regulations, and public administration decisions within a defined jurisdiction.
-
E.
occupation authority section
An occupation authority section is a designated part of a document or system that defines, records, and manages the official powers, responsibilities, and permissions associated with a specific job or role.
- 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_69bd43d71a308190afea7280841b0de8 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:14 p.m.