Triple
T18758745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orontid dynasty |
E458715
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Armavir |
—
|
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: Armavir | Statement: [Orontid dynasty, capital, Armavir]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Armavir Context triple: [Orontid dynasty, capital, Armavir]
-
A.
Armavir
Armavir is a city in southwestern Russia known as an industrial and transportation center on the Kuban River.
-
B.
Skvira
Skvira is a town in Ukraine historically associated with the Skver Hasidic dynasty and its Jewish community.
-
C.
Solvychegodsk
Solvychegodsk is a historic town in northern Russia known for its former salt industry and rich architectural heritage, including notable Orthodox churches.
-
D.
Armavir Province
chosen
Armavir Province is a region in western Armenia known as a historical and religious center, notably home to the spiritual heart of the Armenian Apostolic Church.
-
E.
Ekaterinodar
Ekaterinodar, now known as Krasnodar, was a major city in southern Russia that served as an important political and military center in the Kuban region.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e579f42d0881909bd9ca9c7916516a |
completed | April 20, 2026, 12:57 a.m. |
Created at: April 10, 2026, 11:52 a.m.