Triple
T9960879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Лев |
E195563
|
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.
hasParticularSignificanceFor
Indicates that something holds a special, notable, or contextually important relevance or impact for a particular entity or situation.
-
B.
correspondsToLatinWord
Indicates that one element is the equivalent or matching term of another element in Latin.
-
C.
symbolizes
chosen
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
D.
symbolCombines
Indicates that multiple symbols are merged or joined together to form a single composite symbol or representation.
-
E.
linguisticSignificance
Indicates the degree to which something is important, influential, or meaningful within a particular language or linguistic 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_69ca82eaaa008190a54fa1a9f954b9ad |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb6d219c48190b2084b0eb07ae125 |
completed | April 2, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:47 p.m.