Triple
T6119729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FRBNF11864601 |
E136451
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | authority identifier |
C1033
|
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: authority identifier Context triple: [FRBNF11864601, instanceOf, authority identifier]
-
A.
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.
-
B.
bibliographic identifier
chosen
A bibliographic identifier is a standardized code or string that uniquely distinguishes a specific published or unpublished bibliographic resource within catalogs, databases, or information systems.
-
C.
taxonomic authority
A taxonomic authority is the scientist or group of scientists who first validly publish and formally describe a taxon, often cited alongside the scientific name to indicate its original source.
-
D.
authority control file
An authority control file is a structured database that standardizes names, subjects, and titles to ensure consistent identification and retrieval of entities across bibliographic and information systems.
-
E.
appointing authority
An appointing authority is an individual or entity legally empowered to select, hire, promote, or otherwise make official personnel decisions for positions within an organization or governmental body.
- 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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:14 p.m.