Triple
T34502541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Медаль «За трудовую доблесть» |
E885794
|
entity |
| Predicate | hasRibbonMount |
P34295
|
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: [Медаль «За трудовую доблесть», hasRibbonMount, пятиугольная колодка]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRibbonMount Context triple: [Медаль «За трудовую доблесть», hasRibbonMount, пятиугольная колодка]
-
A.
indicatesOnRibbon
Indicates that one entity is displayed or marked on a ribbon associated with another entity.
-
B.
hasMountingFeature
chosen
Indicates that one entity includes or provides a structural feature intended for mounting or attaching another entity.
-
C.
hasRim
Indicates that one entity possesses or is equipped with a rim as a defining part or feature.
-
D.
hasMottoRibbon
Indicates that an entity features or is associated with a ribbon element specifically used to display a motto.
-
E.
hasInsigniaComponent
Indicates that an entity includes, bears, or is composed of a particular insignia or emblem as one of its components.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 1, 2026, 2:01 a.m.