Triple
T553948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bering Strait |
E11900
|
entity |
| Predicate | languageOriginOfName |
P1754
|
FINISHED |
| Object | named from Danish explorer Vitus Bering |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: named from Danish explorer Vitus Bering | Statement: [Bering Strait, languageOriginOfName, named from Danish explorer Vitus Bering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOriginOfName Context triple: [Bering Strait, languageOriginOfName, named from Danish explorer Vitus Bering]
-
A.
hasNameOrigin
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
B.
etymologyStatus
Indicates the status or reliability classification of an etymological explanation for a term or name.
-
C.
etymologyType
Indicates the specific kind or category of etymological relationship that links a term to its linguistic origin or source.
-
D.
etymologicalSource
Indicates that one term or name originates from, is derived from, or has its roots in another term or name.
-
E.
hasLanguageOfOrigin
chosen
Indicates that one entity has its origin or source in the language specified by another entity.
- F. None of above.
Provenance (3 batches)
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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4991c524481908b2bb88c4feabec6 |
completed | March 1, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69a494bc1f8c8190904356f3a8e801de |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.