Triple
T19252862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flag of the Armenian Soviet Socialist Republic |
E481438
|
entity |
| Predicate | hammerAndSickleColor |
P135057
|
FINISHED |
| Object | gold |
—
|
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: gold | Statement: [Flag of the Armenian Soviet Socialist Republic, hammerAndSickleColor, gold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hammerAndSickleColor Context triple: [Flag of the Armenian Soviet Socialist Republic, hammerAndSickleColor, gold]
-
A.
centralInescutcheon
Indicates that one element serves as a smaller central shield or emblem placed over the main shield or field of another element.
-
B.
heraldicTinctureRed
Indicates that an entity in a heraldic context is colored or depicted with the red tincture (gules).
-
C.
coatOfArms
Indicates that one entity serves as the heraldic emblem or coat of arms representing another entity.
-
D.
flagOrInsignia
Indicates that one entity serves as a flag, emblem, or insignia representing another entity.
-
E.
usesSovietSymbols
Indicates that an entity employs or displays symbols associated with the former Soviet Union.
- 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_69d8e8cd9d1081908a181d02b88b59b8 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fb31f8ac81909cd9a417b60f86a8 |
completed | April 20, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e4dd002d00819088b625056edfb74e |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:28 p.m.