Triple
T38552192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marshal Sovetskogo Soyuza |
E925140
|
entity |
| Predicate | wearerInsignia |
P9510
|
FINISHED |
| Object | large marshal star |
—
|
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: large marshal star | Statement: [Marshal Sovetskogo Soyuza, wearerInsignia, large marshal star]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wearerInsignia Context triple: [Marshal Sovetskogo Soyuza, wearerInsignia, large marshal star]
-
A.
wearsInsigniaAt
Indicates that an entity is wearing or displaying a particular insignia at a specified location or point in time.
-
B.
hasInsigniaWornBy
chosen
Indicates that a particular insignia is worn by a specified entity (such as a person, group, or organization).
-
C.
hasInsigniaComponent
Indicates that an entity includes, bears, or is composed of a particular insignia or emblem as one of its components.
-
D.
symbolOnInsignia
Indicates that a particular symbol appears on or is featured as part of an insignia.
-
E.
wearerBranch
Indicates that one entity serves as the organizational branch or division to which the wearer of an item or uniform is affiliated.
- 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_69f76eaeb69c8190b367df9330d6f6af |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcd318ae38819092ebab2d75be2194 |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f81cbc8190b4fd3bfc3106c1f3 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:32 p.m.