Triple
T10697380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of the RSFSR (1937) |
E252179
|
entity |
| Predicate | definesStateSymbol |
P82723
|
FINISHED |
| Object | state emblem of the RSFSR |
—
|
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: state emblem of the RSFSR | Statement: [Constitution of the RSFSR (1937), definesStateSymbol, state emblem of the RSFSR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesStateSymbol Context triple: [Constitution of the RSFSR (1937), definesStateSymbol, state emblem of the RSFSR]
-
A.
symbolForState
chosen
Indicates that one entity serves as the symbolic representation (such as an icon, emblem, or notation) used to denote or stand for a particular state of another entity.
-
B.
definesStateName
Indicates that an entity specifies or assigns the official name of a state.
-
C.
symbolizedIn
Indicates that one entity serves as a symbol or representation of another entity.
-
D.
definesSyntax
Indicates that one entity specifies or determines the formal structure, rules, or grammar by which another entity is expressed or interpreted.
-
E.
symbolType
Indicates the classification or category of a symbol based on its role, form, or function within a given system.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd89390c8190969ab2b4a79d5818 |
completed | April 9, 2026, 1:14 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8cc0788190b4c02a772e4b58b3 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:12 p.m.