Triple
T14486304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AZT |
E359235
|
entity |
| Predicate | usedInTranscaucasia |
P114415
|
FINISHED |
| Object | yes |
—
|
LITERAL 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: yes | Statement: [AZT, usedInTranscaucasia, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInTranscaucasia Context triple: [AZT, usedInTranscaucasia, yes]
-
A.
includesCaucasusStates
Indicates that a set, group, or region contains one or more of the states located in the Caucasus region.
-
B.
includesCentralAsianStates
Indicates that the referenced set, group, or entity composition contains one or more Central Asian states as members or components.
-
C.
partOfFormerSovietRepublic
Indicates that one entity was a territorial or administrative component of a country that was formerly a republic of the Soviet Union.
-
D.
usedInFormerEasternBlocCountry
Indicates that something was used within a country that was part of the former Eastern Bloc.
-
E.
endDateAsPartOfTranscaucasianSFSR
Indicates the date on which something (such as a status, membership, or existence) ended while it was part of the Transcaucasian Soviet Federative Socialist Republic.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de924ee0f08190baf68318b41fa64d |
completed | April 14, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:20 a.m.