Triple
T18415987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulgarian Antarctic Place-names Commission |
E441890
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | national naming authority |
C2077
|
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: national naming authority Context triple: [Bulgarian Antarctic Place-names Commission, instanceOf, national naming authority]
-
A.
geographical names authority
chosen
A geographical names authority is an entity or system responsible for standardizing, maintaining, and providing authoritative information on the official names and spellings of geographic places.
-
B.
national internet registry
A national internet registry is an organization responsible for allocating and managing internet number resources (such as IP addresses and AS numbers) within a specific country or territory, typically under the broader coordination of a regional internet registry.
-
C.
national mapping agency
A national mapping agency is a government organization responsible for producing, maintaining, and distributing authoritative geographic and cartographic information for an entire country.
-
D.
national register
A national register is an official, government-maintained database that systematically records and tracks specific categories of information—such as citizens, properties, or cultural assets—at the country level.
-
E.
national association
A national association is an organized body that represents and coordinates the interests, standards, and activities of a specific profession, industry, or cause across an entire country.
- 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:47 a.m.