Triple
T13336875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sorbian people |
E317716
|
entity |
| Predicate | autonym |
P1435
|
FINISHED |
| Object | Serby |
E366158
|
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: Serby | Statement: [Sorbian people, autonym, Serby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Serby Context triple: [Sorbian people, autonym, Serby]
-
A.
Serby
chosen
Serby is the endonym used by the Sorbs, a West Slavic ethnic minority primarily living in eastern Germany, to refer to themselves or their language.
-
B.
Byley
Byley is a small rural village in Cheshire, England, situated near the town of Middlewich.
-
C.
Orbey
Orbey is a commune in the Haut-Rhin department of northeastern France, situated in the Vosges mountains within the Alsace region.
-
D.
Sarny
Sarny is a town in western Ukraine known as a local administrative and transportation center in Rivne Oblast.
-
E.
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.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99d00b75c8190af98784c7df904c8 |
completed | April 11, 2026, 12:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f71f3bb06c8190beaf6dfbba9ff613 |
completed | May 3, 2026, 10:11 a.m. |
Created at: April 9, 2026, 9:31 p.m.