Triple
T9401806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elbing |
E226489
|
entity |
| Predicate | historicalName |
P65
|
FINISHED |
| Object | Elbings |
E336100
|
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: Elbings | Statement: [Elbing, historicalName, Elbings]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Elbings Context triple: [Elbing, historicalName, Elbings]
-
A.
Elbling
chosen
Elbling is an ancient white wine grape variety primarily cultivated in Germany and Luxembourg, known for producing light, crisp, and high-acidity wines.
-
B.
Ehling
Ehling is a German-language surname, likely of similar origin and meaning to the related name Ehle.
-
C.
Tesseney
Tesseney is a town in western Eritrea near the Sudanese border, serving as a local commercial and agricultural center in the Gash-Barka region.
-
D.
Elswick
Elswick is a district in Newcastle upon Tyne, England, historically known as a major industrial and shipbuilding center.
-
E.
Oberems
Oberems is a village and municipal district within the municipality of Glashütten in the Hochtaunus region of Hesse, Germany.
- 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_69ca843170f88190800a8ab2b5fc568e |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd51be35cc8190bafad423a142c305 |
completed | April 1, 2026, 5:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1012ca6c0819098c427233d226dd2 |
completed | April 4, 2026, 12:16 p.m. |
Created at: March 30, 2026, 7:46 p.m.