Triple
T30226245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maykopsky District |
E768486
|
entity |
| Predicate | hasNameInAdyghe |
P195047
|
FINISHED |
| Object | Мыекъуапэ къедзыгъо |
—
|
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: Мыекъуапэ къедзыгъо | Statement: [Maykopsky District, hasNameInAdyghe, Мыекъуапэ къедзыгъо]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInAdyghe Context triple: [Maykopsky District, hasNameInAdyghe, Мыекъуапэ къедзыгъо]
-
A.
hasNameInTigrinya
Indicates that an entity is associated with a specific name expressed in the Tigrinya language.
-
B.
nameInAbkhaz
Indicates that an entity’s name is given in the Abkhaz language.
-
C.
hasNameInAzerbaijani
Indicates that an entity is known by a specific name when expressed in the Azerbaijani language.
-
D.
hasNameInAlbanian
Indicates that an entity is associated with a specific name or label expressed in the Albanian language.
-
E.
GeorgianName
Indicates that an entity has a name that is in the Georgian language or follows Georgian naming conventions.
- F. None of above. chosen
Provenance (4 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_69f2248108208190be60bf1af343ce70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
| PDg | Predicate description generation | batch_69fd9fef7aac819089cc88dd3d00296d |
completed | May 8, 2026, 8:33 a.m. |
Created at: April 29, 2026, 7:36 p.m.