Triple
T33469433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coat of arms of the Lithuanian SSR |
E857144
|
entity |
| Predicate | positionOfHammerAndSickle |
P34701
|
FINISHED |
| Object | center |
—
|
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: center | Statement: [Coat of arms of the Lithuanian SSR, positionOfHammerAndSickle, center]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOfHammerAndSickle Context triple: [Coat of arms of the Lithuanian SSR, positionOfHammerAndSickle, center]
-
A.
hammerAndSickleColor
Indicates that a hammer and sickle symbol is depicted in a specified color.
-
B.
positionOnSovietModel
Indicates a stance, policy, or alignment that follows or is modeled closely on the Soviet political, economic, or ideological system.
-
C.
coatOfArmsPosition
Indicates the spatial placement or arrangement of a coat of arms relative to another object, surface, or reference frame.
-
D.
symbolizesNationalSovereignty
Indicates that something serves as a representation or emblem of a nation's sovereignty or independent authority.
-
E.
positionOfEmblem
chosen
Indicates the spatial placement or location of an emblem relative to a reference object or surface.
- 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_69f34973461481909c701c98ebd75623 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff17be6ad48190963206f2619b1b28 |
completed | May 9, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69ff1724ba24819092c928fcbcb286ec |
completed | May 9, 2026, 11:14 a.m. |
Created at: May 1, 2026, 1:37 a.m.