Triple
T20442306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gera |
E501425
|
entity |
| Predicate | nameTransliteration |
P5923
|
FINISHED |
| Object | Gera |
—
|
NE NERFINISHED |
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: Gera | Statement: [Gera, nameTransliteration, Gera]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gera Context triple: [Gera, nameTransliteration, Gera]
-
A.
Gera
Gera is a biblical figure mentioned in the Hebrew Bible, known primarily as a Benjamite ancestor in the genealogy of the tribe of Benjamin.
-
B.
Gera
Gera is a river in Thuringia, Germany, that flows through the city of Erfurt before joining the Unstrut.
-
C.
Gera
Gera is a village on the Greek island of Lesbos, known for its traditional character and location near the Bay of Gera.
-
D.
Gera
Gera is a city in the German state of Thuringia, known for its industrial heritage and historic architecture along the White Elster river.
-
E.
Gera River
The Gera River is a waterway in central Germany that flows through the city of Erfurt in the state of Thuringia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide. chosen
Provenance (2 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_69e0b4ac0a1c81908845d0f8a56abce8 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e685f3b794819080745b135a305ba7 |
completed | April 20, 2026, 8 p.m. |
Created at: April 16, 2026, 11:32 a.m.