Triple
T16736145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hadrut |
E406722
|
entity |
| Predicate | postSovietStatus |
P124441
|
FINISHED |
| Object | part of disputed Nagorno-Karabakh region |
—
|
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: part of disputed Nagorno-Karabakh region | Statement: [Hadrut, postSovietStatus, part of disputed Nagorno-Karabakh region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postSovietStatus Context triple: [Hadrut, postSovietStatus, part of disputed Nagorno-Karabakh region]
-
A.
partOfFormerSovietRepublic
Indicates that one entity was a territorial or administrative component of a country that was formerly a republic of the Soviet Union.
-
B.
statusInSovietUnion
Indicates the legal, social, or political standing an entity held within the Soviet Union.
-
C.
countryBefore1991
Indicates that the specified country existed or held the relevant status prior to the year 1991.
-
D.
countryAfterDissolution
Indicates that one country emerged or existed as a successor state following the dissolution of another country.
-
E.
sovereignStateAfter
Indicates that one sovereign state succeeds another as its political or legal successor in time.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c3a86848190a03f243dd1bdb899 |
completed | April 18, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:20 a.m.