Triple
T2033766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ge'ez |
E44574
|
entity |
| Predicate | ISO639-2Code |
P208
|
FINISHED |
| Object | gez |
E68214
|
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: gez | Statement: [Ge'ez, ISO639-2Code, gez]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: gez Context triple: [Ge'ez, ISO639-2Code, gez]
-
A.
Geg
Geg is an alternative name for Gheg, the northern dialect group of the Albanian language spoken primarily in northern Albania and surrounding regions.
-
B.
.ge
.ge is the country code top-level domain (ccTLD) assigned to websites associated with Georgia.
-
C.
GER
GER is the official FIFA country code used to represent the Germany national football team in international competitions and records.
-
D.
Geez
chosen
Geez is an ancient South Semitic language of Ethiopia and Eritrea, best known today as the liturgical language of the Ethiopian and Eritrean Orthodox Tewahedo Churches.
-
E.
GEKUT
GEKUT is the UN/LOCODE identifier for the city of Kutaisi in Georgia, used in international trade and transport logistics.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb93387488190ac9d8d2746451f2e |
completed | March 7, 2026, 5:35 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae1ff03d3c8190adef0224aac989bd |
completed | March 9, 2026, 1:18 a.m. |
Created at: March 4, 2026, 7:39 p.m.