Triple
T4844810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | state emblem of the Soviet Union |
E108262
|
entity |
| Predicate | officiallyApproved |
P40249
|
FINISHED |
| Object | 1923 |
—
|
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: 1923 | Statement: [state emblem of the Soviet Union, officiallyApproved, 1923]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officiallyApproved Context triple: [state emblem of the Soviet Union, officiallyApproved, 1923]
-
A.
approvedBy
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
B.
approvedAt
chosen
Indicates the date and time at which an entity received formal approval.
-
C.
approvedAs
Indicates that one entity has been officially accepted, authorized, or validated in a particular role, status, or capacity by another entity.
-
D.
areOfficialIn
Indicates that an entity holds an official role, position, or capacity within another entity (such as an organization, institution, or jurisdiction).
-
E.
approvedInCountry
Indicates that an entity has received official authorization or approval within the jurisdiction of a specified country.
- 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_69bd4409b264819085ab855f3eb5381a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e01872c81909607010c10538ad1 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2375a4819098e16acb982c8fab |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:25 p.m.