Triple
T36464842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borchali |
E898394
|
entity |
| Predicate | historicalNameInAzerbaijani |
P203159
|
FINISHED |
| Object | Borçalı |
—
|
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: Borçalı | Statement: [Borchali, historicalNameInAzerbaijani, Borçalı]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalNameInAzerbaijani Context triple: [Borchali, historicalNameInAzerbaijani, Borçalı]
-
A.
historicalNameInArmenian
Indicates that an entity has a specific historical name or designation when expressed in the Armenian language.
-
B.
hasNameInAzerbaijani
Indicates that an entity is known by a specific name when expressed in the Azerbaijani language.
-
C.
historicalNameInUkrainian
Indicates that an entity has a specific historical name or designation when expressed in the Ukrainian language.
-
D.
historicalNameGivenBy
Indicates that one entity is the name historically assigned to another entity by a specific source, culture, or period.
-
E.
historicalNameInEnglish
Indicates that an entity is associated with a historical English-language name by which it was known in the past.
- 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_69f76e58ebd88190b75d9b169b59d793 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a012efebda88190a90c8f650e4b1ee9 |
completed | May 11, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_6a01298cc604819087c836659c128926 |
completed | May 11, 2026, 12:57 a.m. |
| PDg | Predicate description generation | batch_6a012efdf4f08190a006136f7b48da15 |
completed | May 11, 2026, 1:21 a.m. |
Created at: May 3, 2026, 4:10 p.m.