Triple
T15208036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bering |
E363440
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Vitus |
E363016
|
NE 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: Vitus | Statement: [Bering, givenName, Vitus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vitus Context triple: [Bering, givenName, Vitus]
-
A.
Vitus
chosen
Vitus is a masculine given name of Latin origin, historically associated with the Christian saint and later borne by notable figures such as explorer Vitus Bering.
-
B.
Olaus
Olaus is a Latinized form of the Old Norse name Óláfr, historically used in Scandinavian and ecclesiastical contexts.
-
C.
Vitte
Vitte is the largest village and main tourist and administrative center on the Baltic Sea island of Hiddensee in Germany.
-
D.
Helvius
Helvius is an ancient Roman family name (nomen) associated with members of the Helvia gens, such as the physician Helvius Successus.
-
E.
Ehrwald
Ehrwald is a picturesque Austrian village in Tyrol, known as a popular alpine resort and gateway to the Zugspitze massif.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a0b78bc8190b6e5ad51a2c4cfc5 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e006b8e2788190bd1831762e4181ae |
completed | April 15, 2026, 9:44 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fed33dbda08190a10ba81082d0d183 |
completed | May 9, 2026, 6:25 a.m. |
Created at: April 10, 2026, 3:11 a.m.