Triple
T19959291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emblem of the Azerbaijan Soviet Socialist Republic |
E479767
|
entity |
| Predicate | emblemFamily |
P138030
|
FINISHED |
| Object | emblems of Soviet Socialist Republics |
—
|
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: emblems of Soviet Socialist Republics | Statement: [Emblem of the Azerbaijan Soviet Socialist Republic, emblemFamily, emblems of Soviet Socialist Republics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emblemFamily Context triple: [Emblem of the Azerbaijan Soviet Socialist Republic, emblemFamily, emblems of Soviet Socialist Republics]
-
A.
emblemName
Indicates that a specified name is the official or recognized title of an emblem.
-
B.
emblematicFor
Indicates that something serves as a representative symbol or characteristic example of something else.
-
C.
emblemFeatures
Indicates that an emblem includes or displays specific visual elements or characteristics.
-
D.
emblemUsedBy
Indicates that a particular emblem is adopted or employed by a specific entity as its symbol or identifying mark.
-
E.
featuresFamilyName
Indicates that an entity is associated with or displays a particular family name.
- 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65af2c3548190a44f972a1bd33256 |
completed | April 20, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c42c688190a22f4d31ec692377 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:54 p.m.