Triple
T12620619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Дружба народов |
E301368
|
entity |
| Predicate | символизирует |
P129
|
FINISHED |
| Object | дружба между народами |
—
|
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: дружба между народами | Statement: [Дружба народов, символизирует, дружба между народами]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: символизирует Context triple: [Дружба народов, символизирует, дружба между народами]
-
A.
symbolizes
chosen
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
B.
symbolizedIn
Indicates that one entity serves as a symbol or representation of another entity.
-
C.
reconstructionSymbolizes
Indicates that a reconstruction serves as a symbolic representation or stand-in for something else, such as an original object, event, or concept.
-
D.
hasParticularSignificanceFor
Indicates that something holds a special, notable, or contextually important relevance or impact for a particular entity or situation.
-
E.
typicalSymbol
Indicates that something serves as a characteristic or commonly recognized symbol representing something else.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b195108190ac25bd95e644ace4 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:13 p.m.