Triple
T29547299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xankəndi |
E749663
|
entity |
| Predicate | locatedInCountryDuringSovietEra |
P75815
|
FINISHED |
| Object | Azerbaijan SSR |
—
|
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: Azerbaijan SSR | Statement: [Xankəndi, locatedInCountryDuringSovietEra, Azerbaijan SSR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCountryDuringSovietEra Context triple: [Xankəndi, locatedInCountryDuringSovietEra, Azerbaijan SSR]
-
A.
homeCountryDuringSovietEra
chosen
Indicates the country that was considered an entity’s home country during the period of the Soviet Union’s existence.
-
B.
statusInSovietUnion
Indicates the legal, social, or political standing an entity held within the Soviet Union.
-
C.
ownerDuringUSSR
Indicates that one entity was the owner of another entity specifically during the period of the USSR’s existence.
-
D.
timePeriodAsPartOfSovietUnion
Indicates that a specified time period falls within the historical span during which an entity was part of the Soviet Union.
-
E.
usedInFormerEasternBlocCountry
Indicates that something was used within a country that was part of the former Eastern Bloc.
- F. None of above.
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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a003f6083608190a5deadc7291cf70e |
completed | May 10, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_6a003c935c40819085fdb255a52ba03b |
completed | May 10, 2026, 8:06 a.m. |
Created at: April 28, 2026, 5:08 p.m.