Triple
T35141031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MasterSource |
E1014701
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | authoritative data source |
C1037
|
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: authoritative data source Context triple: [MasterSource, instanceOf, authoritative data source]
-
A.
leading authority
A leading authority is an individual or organization widely recognized for having the highest level of expertise, credibility, and influence in a particular field or subject area.
-
B.
bibliographic authority data set
chosen
A bibliographic authority data set is a structured collection of standardized records that uniquely identify and describe entities (such as persons, organizations, works, and subjects) used to control and link names and headings in bibliographic and library catalogs.
-
C.
scientific authority
A scientific authority is an individual or institution recognized for its expertise, credibility, and influence in generating, validating, and communicating scientific knowledge within a particular domain.
-
D.
combined authority
A combined authority is a legal entity formed by two or more local government areas that collaborate to exercise shared strategic powers and responsibilities, typically over transport, economic development, and regional planning.
-
E.
authoritative name server
An authoritative name server is a DNS server that provides definitive, original answers for specific domain names based on data it directly manages, rather than relying on cached or forwarded information.
- 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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.