Triple
T28767453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Velvet Revolution in Czechoslovakia |
E726313
|
entity |
| Predicate | mediaSymbol |
P30078
|
FINISHED |
| Object | jingling of keys at demonstrations |
—
|
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: jingling of keys at demonstrations | Statement: [Velvet Revolution in Czechoslovakia, mediaSymbol, jingling of keys at demonstrations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mediaSymbol Context triple: [Velvet Revolution in Czechoslovakia, mediaSymbol, jingling of keys at demonstrations]
-
A.
communicationSymbol
Indicates a relationship where one entity serves as a symbol or sign used for communication by or between other entities.
-
B.
mediaUse
Indicates that an entity makes use of, consumes, or engages with a particular medium or media resource.
-
C.
mediaLabel
Indicates that a media item is associated with a specific label or tag that characterizes or categorizes it.
-
D.
mediaName
Indicates the name or title assigned to a media item (such as a work, file, or publication) in the relationship.
-
E.
iconOf
chosen
Indicates that one entity serves as a symbolic or representative image or emblem of another entity.
- 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_69f03198be14819098fa74e48b3749bf |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 6:14 a.m.